Skip to main content

Measuring Top Domains: SPF, DMARC, and MTA-STS

Live DNS queries of 152 top global domains reveal high adoption and strict enforcement of SPF and DMARC, while transport security lags behind.

AI-written
Inewgen
14 Sep 2026Source: Dev.to3 min read (0 views)
Share
Measuring Top Domains: SPF, DMARC, and MTA-STS

Stock photo for illustration only, not from the actual event

Font size
  • Queried live DNS records for 152 top domains to measure email security adoption
  • Most major domains enforce strict DMARC p=reject policies rather than monitoring
  • Transport security standard MTA-STS remains adopted by only 9.2% of domains
  • Configuration friction and complexity explain the slow adoption of MTA-STS

Protocols like SPF, DMARC, and MTA-STS act as essential DNS records preventing malicious actors from spoofing emails from your domain. While experts universally recommend configuring them, the actual implementation status among top-tier websites remains a critical question. Researchers queried live DNS records for 152 of the most frequently used domains to evaluate whether top web properties genuinely protect their email infrastructure, discovering that while fundamentals are well handled, newer transport standards remain widely overlooked.

Out of the 152 domains analyzed, 146 actively receive mail by publishing MX records. Among this active subset, the adoption rates for foundational authentication standards are exceptionally high, though the advanced standard drops off sharply.

146Domains actively receiving mail out of 152 tested
75%Enforce strict DMARC p=reject policy setting
9.2%Domains utilizing the MTA-STS transport standard

A DMARC record can sometimes be merely decorative, as the p= policy dictates how receiving servers handle messages failing authentication. Therefore, the core question is not just whether domains publish DMARC, but whether they actively enforce it. At the upper echelon of the web, they certainly do: 114 out of 152 domains deploy p=reject, the strictest setting available, while 26 use p=quarantine, and only 10 remain at monitor-only p=none settings.

chromebook notebook computer office desk workspace

Stock photo for illustration only, not from the actual event

These figures demonstrate that 75% of the evaluated domains utilize the strictest policy, and 93% of those publishing DMARC actively enforce it. The common half-measure of publishing a record and leaving it on monitor-only mode indefinitely is exceptionally rare among these large-scale domains.

Never miss the latest news?

Subscribe to get news summaries by email - not often enough to be annoying.

โฆษณา

The heavy preference for p=reject over monitor-only policies highlights strong operational confidence among leading organizations. Enforcing strict rejection cuts off potential phishing threats immediately, but requires precise internal mail configurations to avoid delivery blockages, signaling high technical maturity.

While SPF and DMARC authenticate message senders, they do nothing to secure transit between mail servers. MTA-STS closes this gap by publishing policies requiring delivery over TLS without falling back to plaintext, defeating downgrade attacks on the wire. It represents the natural next step following DMARC, yet among these top domains, a mere 9.2% have implemented it.

The primary barrier is configuration friction. While SPF and DMARC require single TXT records, MTA-STS requires a hosted policy file on an mta-sts subdomain alongside additional DNS records. This complexity leaves most organizations hesitant. If you have already established DMARC and seek genuine security gains, MTA-STS offers the next logical milestone.

Source: Dev.to

Comments

Leave a Comment
0/2000

Found something wrong in this article? Report an issue with this article