RESEARCH DOSSIER / 2026
Across 999 of 1,000 observed Tranco-ranked domains, 71.9% published valid DMARC and 83.1% of those publishers enforced quarantine or rejection. This is direct public-DNS measurement of ranked domains—not a brand-value, deliverability or incident score.
WHY THIS MATTERSThis DNS benchmark measures a domain owner’s published direction for failing mail—not inbox placement or fraud—but an enforcing policy gives participating receivers more instruction when a forged exact-domain message fails aligned authentication.
71.9%
DMARC adoption
718 of 999
83.1%
Enforcement among publishers
597 of 718
6.8%
Publishers without aggregate reporting
49 of 718
2.8%
SPF recursive lookup failures
21 of 756
NAMED-ROW DATA
Each row is the exact Tranco-ranked hostname scanned in the recorded window. Tranco rank is a web-domain popularity signal, not a corporate revenue or brand-value score. The CSV and JSON contain the full published field set, including MX answers and aggregate-report destination domains without mailbox local parts.
| Rank | Domain | DMARC | Reporting | SPF | SPF lookups | BIMI | Observed MX | Observation |
|---|---|---|---|---|---|---|---|---|
| 501 | behance.net | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: rua.agari.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | Google Workspace 10:aspmx.l.google.com · 20:alt1.aspmx.l.google.com · 20:alt2.aspmx.l.google.com · 30:aspmx2.googlemail.com · 30:aspmx3.googlemail.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 502 | shein.com | quarantine p=quarantine · pct=100 Strict alignment: DKIM no · SPF no | Published To: shein.com | valid Records: 1 · all=softfail | 7 Direct: 3 · total: 7 | Published Logo yes · VMC yes | Unknown operator 5:mx-shein-com.icoremail.net · 10:mx.sheincorp.cn | Observed Aug 17, 2026, 02:52 PM UTC |
| 503 | tencent-cloud.net | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 504 | fandom.com | quarantine p=quarantine · pct=100 Strict alignment: DKIM no · SPF no | Published To: fandom.com | valid Records: 1 · all=fail | 9 Direct: 8 · total: 9 | Not published | Google Workspace 1:aspmx.l.google.com · 5:alt1.aspmx.l.google.com · 5:alt2.aspmx.l.google.com · 10:aspmx2.googlemail.com · 10:aspmx3.googlemail.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 505 | gcdn.co | no valid DMARC | Not observed | valid Records: 1 | 7 Direct: 1 · total: 7 | Not published | Unknown operator 20:mail.gcdn.co | Observed Aug 17, 2026, 02:52 PM UTC |
| 506 | foxnews.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: emaildefense.proofpoint.com | valid Records: 1 · all=fail | 5 Direct: 5 · total: 5 | Not published | Recognized gateway 10:mxa-00195501.gslb.pphosted.com · 10:mxb-00195501.gslb.pphosted.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 507 | chinamobile.com | none p=none · pct=100 Strict alignment: DKIM no · SPF no | Published To: chinamobile.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | Unknown operator 5:mx.chinamobile.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 508 | mediatek.com | quarantine p=quarantine · pct=100 Strict alignment: DKIM no · SPF no | Published To: mediatek.com | valid Records: 1 · all=fail | 7 Direct: 5 · total: 7 | Not published | Unknown operator 10:mailgw01.mediatek.com · 10:mailgw02.mediatek.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 509 | att.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: emaildefense.proofpoint.com | valid Records: 1 · all=softfail | 1 Direct: 1 · total: 1 | Published Logo yes · VMC yes | Recognized gateway 10:mx0a-00191d01.pphosted.com · 10:mx0b-00191d01.pphosted.com · 20:mxa-00191d01.gslb.pphosted.com · 20:mxb-00191d01.gslb.pphosted.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 510 | indiatimes.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: indiatimes.com | invalid: multiple-records Records: 2 | — Direct: 0 · total: | Not published | Unknown operator 5:bounce.indiatimes.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 511 | amzn.to | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: dmarc.amazon.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 512 | blogger.com | quarantine p=quarantine · pct=100 Strict alignment: DKIM no · SPF no | Published To: google.com | valid Records: 1 | 1 Direct: 1 · total: 1 | Not published | Unknown operator 5:gmr-smtp-in.l.google.com · 10:alt1.gmr-smtp-in.l.google.com · 10:alt2.gmr-smtp-in.l.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 513 | mcafee.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: vali.email, rep.dmarcanalyzer.com | valid Records: 1 · all=fail | 1 Direct: 1 · total: 1 | Published Logo yes · VMC yes | Microsoft 365 10:mcafee-com.mail.protection.outlook.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 514 | google.de | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: google.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | Google Workspace 0:smtp.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 515 | ft.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: ft.com | valid Records: 1 · all=fail | 9 Direct: 7 · total: 9 | Published Logo yes · VMC yes | Unknown operator 10:mxa.germany.inbound.cf-emailsecurity.net · 10:mxb.germany.inbound.cf-emailsecurity.net | Observed Aug 17, 2026, 02:52 PM UTC |
| 516 | google.com.hk | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: google.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | Google Workspace 0:smtp.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 517 | discord.media | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: dmarc-reports.cloudflare.net | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 518 | squarespacedns.com | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 519 | atlassian.net | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: abuse.atlassian.com | valid Records: 1 · all=fail | 6 Direct: 3 · total: 6 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 520 | slideshare.net | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: slideshare.com | valid Records: 1 · all=softfail | 0 Direct: 0 · total: 0 | Not published | Google Workspace 1:smtp.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 521 | 2gis.com | quarantine p=quarantine · pct=100 Strict alignment: DKIM no · SPF no | Not published | valid Records: 1 · all=fail | 9 Direct: 5 · total: 9 | Not published | Unknown operator 10:mx3.2gis.com · 10:mx4.2gis.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 522 | markmonitor.com | quarantine p=quarantine · pct=100 Strict alignment: DKIM no · SPF no | Published To: reports.dmarctrust.com | valid Records: 1 · all=fail | >10 Direct: 2 · total: 11 | Not published | Microsoft 365 0:markmonitor-com.mail.protection.outlook.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 523 | run.app | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: google.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 524 | newrelic.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: newrelic.com, ag.dmarcian.com | valid Records: 1 · all=softfail | 10 Direct: 6 · total: 10 | Not published | Google Workspace 10:aspmx.l.google.com · 20:alt1.aspmx.l.google.com · 30:alt2.aspmx.l.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 525 | firefox.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: vali.email, firefox.com | valid Records: 1 · all=fail | 5 Direct: 5 · total: 5 | Not published | Unknown operator 10:smtp1.mdc1.mozilla.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 526 | bdydns.com | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 527 | ui-dns.com | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 528 | adobedtm.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: rua.agari.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 529 | duckduckgo.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: ag.dmarcian.com | valid Records: 1 · all=fail | 8 Direct: 5 · total: 8 | Not published | Microsoft 365 0:duckduckgo-com.mail.protection.outlook.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 530 | wired.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: inbox.ondmarc.com | valid Records: 1 · all=softfail | 5 Direct: 1 · total: 5 | Published Logo yes · VMC yes | Google Workspace 1:aspmx.l.google.com · 5:alt1.aspmx.l.google.com · 5:alt2.aspmx.l.google.com · 10:alt3.aspmx.l.google.com · 10:alt4.aspmx.l.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 531 | visualstudio.com | no valid DMARC | Not observed | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 532 | vidaahub.com | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 533 | e2ro.com | reject p=reject · pct=100 Strict alignment: DKIM yes · SPF yes | Published To: eero.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 534 | dynatrace.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: vali.email, dmarc.250ok.net, dmarc.cyber.dhs.gov | valid Records: 1 · all=fail | 1 Direct: 1 · total: 1 | Published Logo yes · VMC no | Recognized gateway 10:us-smtp-inbound-1.mimecast.com · 10:us-smtp-inbound-2.mimecast.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 535 | impervadns.net | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 536 | jquery.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Not published | valid Records: 1 · all=fail | 6 Direct: 2 · total: 6 | Not published | Unknown operator 10:mx1.forwardemail.net · 10:mx2.forwardemail.net | Observed Aug 17, 2026, 02:52 PM UTC |
| 537 | svc.ms | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: dmarc.microsoft | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 538 | oup.com | none p=none · pct=100 Strict alignment: DKIM no · SPF no | Published To: rua.easydmarc.eu | valid Records: 1 · all=softfail | 10 Direct: 1 · total: 10 | Not published | Microsoft 365 0:oup-com.mail.protection.outlook.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 539 | elasticbeanstalk.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: dmarc.amazon.com | valid Records: 1 · all=fail | 0 Direct: 0 · total: 0 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 540 | okta.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: emaildefense.proofpoint.com, okta.com | valid Records: 1 · all=softfail | 1 Direct: 1 · total: 1 | Published Logo yes · VMC no | Recognized gateway 10:mxa-00553301.gslb.pphosted.com · 10:mxb-00553301.gslb.pphosted.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 541 | capcut.com | none p=none · pct=100 Strict alignment: DKIM no · SPF no | Published To: bytedance.com | no SPF Records: 0 | — Direct: 0 · total: | Not published | Google Workspace 1:aspmx.l.google.com · 5:alt1.aspmx.l.google.com · 5:alt2.aspmx.l.google.com · 10:alt3.aspmx.l.google.com · 10:alt4.aspmx.l.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 542 | hicloud.com | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 543 | trendmicro.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: dmarcrua.tmes.trendmicro.com | valid Records: 1 · all=fail | 7 Direct: 7 · total: 7 | Published Logo yes · VMC yes | Unknown operator 10:mad666.in.tmes.trendmicro.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 544 | patreon.com | quarantine p=quarantine · pct=100 Strict alignment: DKIM no · SPF no | Published To: patreon.com | valid Records: 1 · all=softfail | 10 Direct: 4 · total: 10 | Not published | Google Workspace 10:aspmx.l.google.com · 20:alt1.aspmx.l.google.com · 20:alt2.aspmx.l.google.com · 30:aspmx2.googlemail.com · 30:aspmx3.googlemail.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 545 | nstld.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: rua.agari.com, verisign.com | no SPF Records: 0 | — Direct: 0 · total: | Not published | Unknown operator 15:eagle.verisign.com · 15:pigeon.verisign.com · 50:citadel.verisign.net · 50:kaos.verisign.net · 100:modor.verisign.net | Observed Aug 17, 2026, 02:52 PM UTC |
| 546 | time.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: time.com | valid Records: 1 · all=fail | 7 Direct: 7 · total: 7 | Published Logo yes · VMC yes | Google Workspace 1:aspmx.l.google.com · 5:alt1.aspmx.l.google.com · 5:alt2.aspmx.l.google.com · 10:alt3.aspmx.l.google.com · 10:alt4.aspmx.l.google.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 547 | usatoday.com | none p=none · pct=100 Strict alignment: DKIM no · SPF no | Published To: vali.email | valid Records: 1 · all=fail | 10 Direct: 7 · total: 10 | Not published | Microsoft 365 5:usatoday-com.mail.protection.outlook.com | Observed Aug 17, 2026, 02:52 PM UTC |
| 548 | cloudflareinsights.com | reject p=reject · pct=100 Strict alignment: DKIM no · SPF no | Published To: dmarc.area1reports.com | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 549 | byteglb.com | no valid DMARC | Not observed | no SPF Records: 0 | — Direct: 0 · total: | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
| 550 | live.net | none p=none · pct=100 Strict alignment: DKIM no · SPF no | Published To: dmarc.microsoft | valid Records: 1 · all=softfail | 5 Direct: 5 · total: 5 | Not published | No published MX | Observed Aug 17, 2026, 02:52 PM UTC |
“No valid DMARC” and “no SPF” describe records observed at the named DNS location during this scan. They do not establish missing mail authentication on every sending subdomain, a delivery outcome, compromise or an incident.
WHY THIS MATTERS
High-visibility web domains are familiar to customers, staff and partners. A missing or monitoring-only DMARC policy leaves less protection at participating receivers when a forged message using the exact visible From domain fails aligned authentication.
Learn how DMARC evaluates a message →01 / DOMAIN IDENTITY
An attacker can send a message that displays the organization's exact domain in the From line. Without a valid DMARC record, participating receivers have no DMARC handling request from that domain owner when aligned SPF and DKIM fail.
02 / PRACTICAL HARM
A forged message can imitate a widely recognized domain in an account, billing, support or delivery workflow. That can make a malicious link or payment request more convincing. A public DNS observation does not show that any such message was sent, delivered or acted on.
THREE DIFFERENT DNS STATES
Risk, not incident evidence: this DNS state does not prove spoofing, fraud, compromise or weak internal controls. DMARC also does not stop lookalike domains, abuse of a compromised legitimate account or every phishing technique.
SCOPE
RESEARCH QUESTIONS
RELEASE RECORD
August 17, 2026
Current Tranco top-1,000 source snapshot pinned
August 17, 2026
Public DNS scan and named-row data package completed
August 17, 2026
Table, CSV and JSON released
The release passed the stated evidence and review gates.
DELIVERY PACKAGE
Media posture
Share the complete methodology and downloadable row data with specialist editors; describe observed DNS configuration without treating a domain as an incident or performance score.
Groups below the 30-domain threshold are suppressed. Every visible percentage includes its numerator and denominator.
| Group | Observed | DMARC | Enforcement | No reporting | SPF lookup failure | BIMI among enforcing |
|---|---|---|---|---|---|---|
| No published MX | 310 | 36.1% (112/310) | 84.8% (95/112) | 8.9% (10/112) | 0% (0/114) | 2.1% (2/95) |
| Unknown operator | 254 | 78.3% (199/254) | 74.9% (149/199) | 13.1% (26/199) | 2.2% (5/227) | 28.2% (42/149) |
| Google Workspace | 225 | 94.2% (212/225) | 87.7% (186/212) | 4.7% (10/212) | 4.2% (9/214) | 35.5% (66/186) |
| Recognized gateway | 98 | 94.9% (93/98) | 89.2% (83/93) | 0% (0/93) | 1.1% (1/93) | 32.5% (27/83) |
| Microsoft 365 | 94 | 92.6% (87/94) | 82.8% (72/87) | 2.3% (2/87) | 5.4% (5/92) | 29.2% (21/72) |
SVG and PNG versions are licensed CC BY 4.0.
CITATION & MEDIA KIT
The aggregate findings and charts are free to quote, republish and build on under CC BY 4.0. Attribute Palisade and link to this report so readers can inspect the methodology and denominators.
Suggested citation
Palisade. “Top 1,000 global web brands email-authentication benchmark 2026.” 2026-08-17. https://www.palisade.email/research/global-top-1000-web-brands-email-authentication-2026
Pinned source snapshot
9007a42efc2f980ac0d2f2c18bd53512cc84737a89d926bfe18feaadc43cabcbOpen the exact ranked source listA reproducible research ranking that combines multiple popularity signals; the report retains the permanent current-list URL for every row.
DMARC discovery, policy and aggregate-reporting semantics used by the DNS parser.
Named rows are limited to direct Tranco source domains and their observed public DNS state. The report does not assign a corporate owner, brand value, deliverability rate, reputation score, compromise finding or phishing incident to any row.