← Back to Scanner

iflix.com

Name: iflix.com Email Security Posture Assessment
Creator: RacterMX

Posture Score: 64/100

Scanned May 8, 2026 at 5:31 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

Multiple SPF records detected

Multiple SPF records cause undefined behavior per RFC 7208. Only one SPF record should exist.

💡 Merge all SPF records into a single TXT record.

critical

No DMARC record found

The domain has no DMARC record, providing no policy for handling unauthenticated email.

💡 Publish a DMARC TXT record at _dmarc.iflix.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@iflix.com").

critical

No NS records found

No nameserver records could be retrieved for this domain.

💡 Ensure NS records are properly configured at your registrar and in your zone file.

critical

No DKIM records found

No DKIM records were found for any common selector. Email may not be authenticated.

💡 Configure DKIM signing and publish the public key at <selector>._domainkey.iflix.com

high

No SOA record found

No SOA record could be retrieved for this domain.

💡 Ensure a valid SOA record is configured in your zone file.

high

Cannot check DNS consistency — no NS records

No nameserver records could be retrieved for consistency checking.

💡 Ensure NS records are properly configured.

high

No MTA-STS record found

Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.

💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.iflix.com/.well-known/mta-sts.txt

medium

STARTTLS without MTA-STS or DANE protection

STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.

💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.

medium

No CAA records found

No CAA records are configured. Any certificate authority can issue certificates for this domain.

💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"

medium

No TLS-RPT record found

Without TLS-RPT, you will not receive reports about TLS negotiation failures.

💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@iflix.com").

low

Very low TTL on A records: 120s

3 A records have a TTL of 120s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

ARC support likely available

MX server software appears to support ARC headers for authentication preservation.

pass

SMTP security checks passed

No open relay, VRFY/EXPN, or banner disclosure issues detected.

pass

SMTP RFC 5321 compliance checks passed

The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.

pass

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

DKIM2 not detected

No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.

informational

Shared/free email hosting detected: alt1.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt2.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt3.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt4.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

No DANE/TLSA records found

DANE is not configured for any MX server. This is optional but provides strong certificate binding.

informational

No BIMI record found

BIMI is not configured. Your brand logo will not display in supporting email clients.

informational

Open mail ports on alt1.aspmx.l.google.com

Detected open mail-related ports: 25

informational

RFC 8058 one-click unsubscribe assessment

No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.

informational

MX IP network diversity

MX IPs span 5 different /16 networks, providing good diversity.

informational

Attack Surface Findings

NSEC records enable zone walking

The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.

💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.

high

LOC record exposes geographic location

A LOC record for iflix.com reveals the physical location of infrastructure. This aids targeted attacks.

💡 Remove the LOC record from public DNS unless geographic information is intentionally published.

medium

Domain enumerability: medium

The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.

💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.

medium

NSEC used instead of NSEC3 (zone enumeration possible)

The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.

💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.

medium

RP record exposes responsible person

An RP (Responsible Person) record for iflix.com reveals contact information: ins-hewub8c0.ias.tencent-cloud.net.. This can be used for social engineering.

💡 Remove the RP record if the contact information is not intended to be public.

low

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

115 subdomain(s) discovered for iflix.com

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

985 certificate(s) found in CT logs

Certificate Transparency logs contain 985 certificate(s) for iflix.com and its subdomains. Each certificate reveals subdomain names.

informational

NSEC3 authenticated denial of existence

The domain uses NSEC3 with -1 iteration(s) and salt '-'.

informational

DNSSEC is enabled

DNSKEY and/or DS records are present, indicating DNSSEC is configured.

informational

Reputation Findings

Missing Strict-Transport-Security on iflix.com

The Strict-Transport-Security header is not set on https://iflix.com.

💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.

medium

security.txt present

Found security.txt at https://iflix.com/.well-known/security.txt.

pass

TLS certificate valid for 148 days

Certificate for iflix.com expires on 2026-10-04.

pass

Certificate issued by GlobalSign Atlas R3 OV TLS CA 2026 Q1

The certificate for iflix.com is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for iflix.com uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for iflix.com uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for iflix.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on iflix.com.

pass

Google Safe Browsing DNS check — no flag detected

DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.

informational

Abuse contact lookup failed

Could not query abuse contact information.

informational

PhishTank — API key required

PhishTank phishing database check requires an API key.

informational

Sender Score — API key required

Sender Score reputation check requires an API key.

informational

Cisco Talos — API key required

Cisco Talos IP reputation check requires an API key.

informational

Could not connect to webmail.iflix.com

HTTPS request to https://webmail.iflix.com failed or timed out.

informational

WHOIS lookup failed

Could not retrieve WHOIS data for iflix.com.

informational

Dependency Chains

DMARC Authentication Chain (SPF)

DMARC uses SPF to verify that emails come from authorized servers

SPF Record SPF record found and configured → DMARC Policy DMARC policy missing

⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.

DMARC Authentication Chain (DKIM)

DMARC uses DKIM to verify that emails have not been tampered with

DKIM Signature DKIM signature missing → DMARC Policy DMARC policy missing

⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.

Mail Server Identity: alt1.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt1.aspmx.l.google.com Mail server at 173.194.76.27 → PTR Record Reverse DNS: ws-in-f27.1e100.net

Mail Server Identity: alt2.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt2.aspmx.l.google.com Mail server at 142.250.102.26 → PTR Record Reverse DNS: rb-in-f26.1e100.net

Mail Server Identity: alt3.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt3.aspmx.l.google.com Mail server at 192.178.213.26 → PTR Record Reverse DNS: yugrqzs-in-f26.1e100.net

Mail Server Identity: alt4.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt4.aspmx.l.google.com Mail server at 142.251.127.27 → PTR Record Reverse DNS: lcfrai-in-f27.1e100.net

Mail Server Identity: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 172.253.116.26 → PTR Record Reverse DNS: dj-in-f26.1e100.net

Mail Server Reputation: alt1.aspmx.l.google.com