Public email posture · checked 2026-09-27

netflix.com: DMARC, SPF and MX report

What public DNS says about how netflix.com authenticates and routes email — read the way a receiving mail server reads it, with every change recorded since 2026-09-26.

grade A · enforcing DMARC with SPF hard failTranco rank 421 snapshot
Observed configurationPublic DNS only. Nothing here required access to netflix.com.
DMARCp=reject
SPF-all
SPF lookups6/10
MX5
DKIM selectorswildcard
MTA-STSno
RecordValue
MX1 aspmx.l.google.com · 5 alt1.aspmx.l.google.com · 5 alt2.aspmx.l.google.com · 10 aspmx2.googlemail.com · 10 aspmx3.googlemail.com
SPFv=spf1 include:_spf_ipv4.netflix.com include:_spf.google.com include:amazonses.com include:servers.mcsv.net include:_spf.salesforce.com include:_spf.createsend.com -all
DMARCv=DMARC1; p=reject; fo=1; rua=mailto:netflix@rua.netcraft.com,mailto:dmarcreports@netflix.com,mailto:dmarc_agg@dmarc.250ok.net;ruf=mailto:netflix@ruf.netcraft.com,mailto:dmarcreports@netflix.com,mailto:dmarc_fr@dmarc.250ok.net
DKIM selectorswildcard record answers every selector
MTA-STS / TLS-RPT / BIMIno / no / no
Providersinbound: Google Workspace · sending: Amazon SES, Google Workspace, Mailchimp
Nameserversns-1372.awsdns-43.org, ns-1984.awsdns-56.co.uk, ns-659.awsdns-18.net, ns-81.awsdns-10.com
Run a live DMARC checkBuild the digital twinLive tools re-query DNS now; this report is the 2026-09-27 snapshot.

What this configuration means

Each section below is shown because the observed records match its condition. The explanations are reviewed text selected by the data, not generated from it.

DMARC enforces rejection

netflix.com publishes p=reject. Receivers that honour DMARC refuse mail using this domain in From unless SPF or DKIM aligns. This is the strongest published posture; it depends on every legitimate sender — including third-party platforms — having an aligned path, and on the aggregate reports the record requests to catch regressions.

DKIM selectors are published

11 selectors resolve under _domainkey.netflix.com: google, selector1, selector2, default, s1, s2, k1, dkim, mail, smtpapi, mandrill. Selector names often identify the sending platform, and each represents a signing key that can produce an aligned DKIM path for DMARC — the path that survives forwarding.

A wildcard answers every DKIM selector

A query for a selector name that cannot exist still returns a record, so *._domainkey.netflix.com is a wildcard. Selector discovery is not meaningful here; every name appears published. Wildcards are typically a null key (p=) used to revoke all selectors, or an accident that masks the real configuration.

No transport-security policy

netflix.com does not publish MTA-STS, so senders negotiate TLS opportunistically and fall back to clear text if an attacker strips the upgrade. Publishing TLS-RPT first, then MTA-STS in testing mode, adds transport protection for inbound mail without risk to delivery.

Sending platforms visible in DNS

Public records reference 3 platforms: Amazon SES, Google Workspace, Mailchimp. Each SPF include or DKIM selector is an authorization that someone must own. Platforms no longer in use remain authorized until the records are removed.

Change history

No change has been observed since the first snapshot on 2026-09-26. The domain is re-checked regularly and a new entry appears here when any record above changes.

How to read this report

The grade summarizes two records only: A means an enforcing DMARC policy with SPF hard fail; B enforcing DMARC with SPF; C monitoring-only DMARC or a weak SPF qualifier; D one of SPF or DMARC missing; F neither published. It is a prioritization aid for the public control plane, not a statement about deliverability, reputation or the security of the organization behind the domain.

DMARC policy is discovered with the RFC 9989 DNS tree walk, so a subdomain with no record of its own is reported with the organizational policy it inherits. DKIM selectors are discovered from common names only; a domain may sign with selectors this check does not try. Everything on this page comes from public DNS as observed on 2026-09-27; caches and split-horizon DNS can show different values elsewhere.

If you operate netflix.com and want a record corrected or the report removed, contact Mailybox.