Email Authentication Check

whitehouse.gov

This check reviews your domain's email authentication setup to help protect against spoofing and phishing.

DMARC SPF BIMI TLS-RPT MTA-STS

All data shown is public and sourced from DNS.

Last checked less than a minute ago

0 out of 110
Very Good

Domain Health Score

Your domain has strong email authentication. A few improvements can get you to a perfect score.

SPF
Sender Policy Framework
26 / 30
DMARC
Domain-based Message Authentication
45 / 50
BIMI
Brand Indicators for Message Identification
20 / 20
TLS
TLS Security (MTA-STS & TLS-RPT)
0 / 10

Top Recommendation

+4

Upgrade to -all (hard fail) for maximum protection

SPF improvement

whitehouse.gov enforces a strict DMARC reject policy, instructing receivers to block unauthenticated emails. SPF is published with a soft fail policy (~all), flagging unauthorized senders without blocking them. Overall, whitehouse.gov has solid email authentication with room for minor improvements.

0

DMARC Check Results

45 / 50 points

Score Breakdown

DMARC record published
+10
Syntax valid
+5
Reject policy (maximum protection)
+20
Aggregate reporting (rua) configured and verified
+10
Forensic reporting (ruf) not configured (optional)
0 / 5

DMARC check passed: properly configured

DMARC record is valid and configured correctly.

_dmarc.whitehouse.gov TXT Entry:

v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]

Policy (p)

reject

DKIM Alignment (adkim)

Relaxed (default)

SPF Alignment (aspf)

Relaxed (default)

Reporting (RUA/RUF)

Aggregate Reports

Configured
[email protected]
[email protected]
External Domain Verification
[email protected]

Verification successful

[email protected]

Verification successful

Learn more about aggregate reports →

Forensic Reports

Not Configured
Learn more about forensic reports →

Add Our Monitoring System

You can add our monitoring system alongside your existing setup. DMARC supports multiple mailto: addresses, giving you additional visibility and backup reporting.

  • Automated DMARC report processing every 5 minutes
  • Track all sending sources and authentication results
  • Email alerts when your DNS records change
Get Started
0

BIMI Check (default selector)

20 / 20 points

Score Breakdown

BIMI record published
+5
BIMI record valid
+5
Logo URL accessible and valid SVG
+5
Verified Mark Certificate (VMC) valid
+5

BIMI Record Found and Looks Good

Current BIMI Entry:

v=BIMI1; l=https://whitehouse.gov/wp-content/themes/whitehouse/assets/svg/wh-bimi-avatar.svg; a=https://whitehouse.gov/.well-known/vmc/executive_office_of_the_president.pem

Logo URL

https://whitehouse.gov/wp-content/themes/whitehouse/assets/svg/wh-bimi-avatar.svg

image/svg+xml

Note: We do not parse SVG content for safety.

Mark Certificate

https://whitehouse.gov/.well-known/vmc/executive_office_of_the_president.pem

Valid PEM detected

0

SPF Record Check Results

26 / 30 points

Score Breakdown

SPF record published
+10
Syntax valid
+5
Soft fail policy (~all)
+6 / 10
No configuration warnings
+5

SPF record is valid.

whitehouse.gov TXT SPF Entry:

v=spf1 include:spf.mail.dmz.pitc.gov include:spf.protection.outlook.com include:spf.mandrillapp.com ip4:214.3.115.10/32 ip4:214.3.115.12/32 ip4:214.3.115.14/32 ip4:214.3.115.225/32 ip4:214.3.140.16/32 ip4:214.3.140.22/32 ip4:214.3.140.255/32 ~all

Syntax Check

OK

DNS Lookup Count

5 / 10 max

Root-level mechanisms requiring DNS queries: 3.

Void Lookups

0 / 2 max

Default Policy

~all

Soft fail: Mark emails from unauthorized servers as suspicious but don't reject

All Authorized IP Addresses

Grouped by DNS record source (includes and sub-includes)

whitehouse.gov (Root SPF Record)
214.3.115.10/32
214.3.115.12/32
214.3.115.14/32
214.3.115.225/32
214.3.140.16/32
214.3.140.22/32
214.3.140.255/32

This record also contains:

include:spf.mail.dmz.pitc.gov include:spf.protection.outlook.com - Microsoft 365 include:spf.mandrillapp.com - Mailchimp Transactional
include:spf-v1.mail.dmz.pitc.gov
214.3.57.81/32
214.3.57.82/32
214.3.60.81/32
214.3.60.82/32
include:spf-v2.mail.dmz.pitc.gov
214.3.57.98/32
214.3.57.99/32
214.3.57.100/32
214.3.60.98/32
214.3.60.99/32
214.3.60.100/32
include:spf.protection.outlook.com | Microsoft 365
40.92.0.0/15
40.107.0.0/16
52.100.0.0/15
52.102.0.0/16
52.103.0.0/17
104.47.0.0/17
2a01:111:f400::/48
2a01:111:f403::/49
2a01:111:f403:8000::/51
2a01:111:f403:c000::/51
2a01:111:f403:f000::/52
include:spf.mandrillapp.com | Mailchimp Transactional
198.2.128.0/24
198.2.132.0/22
198.2.136.0/23
198.2.145.0/24
198.2.186.0/23
205.201.131.128/25
205.201.134.128/25
205.201.136.0/23
205.201.139.0/24
198.2.177.0/24
198.2.178.0/23
198.2.180.0/24

DNS Lookup Details

1
include:
spf.mail.dmz.pitc.gov
Valid

SPF record found

Lookup cost: 2
Included by whitehouse.gov

TXT Record

v=spf1 include:spf-v1.mail.dmz.pitc.gov include:spf-v2.mail.dmz.pitc.gov -all

Processed recursively per RFC 7208

2
include:
spf-v1.mail.dmz.pitc.gov
Valid

SPF record found

Lookup cost: 0
Included by spf.mail.dmz.pitc.gov

TXT Record

v=spf1 ip4:214.3.57.81/32 ip4:214.3.57.82/32 ip4:214.3.60.81/32 ip4:214.3.60.82/32 ~all

Processed recursively per RFC 7208

3
include:
spf-v2.mail.dmz.pitc.gov
Valid

SPF record found

Lookup cost: 0
Included by spf.mail.dmz.pitc.gov

TXT Record

v=spf1 ip4:214.3.57.98/32 ip4:214.3.57.99/32 ip4:214.3.57.100/32 ip4:214.3.60.98/32 ip4:214.3.60.99/32 ip4:214.3.60.100/32 ~all

Processed recursively per RFC 7208

4
include:
spf.protection.outlook.com | Microsoft 365
Valid

SPF record found

Lookup cost: 0
Included by whitehouse.gov

TXT Record

v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all

Processed recursively per RFC 7208

5
include:
spf.mandrillapp.com | Mailchimp Transactional
Valid

SPF record found

Lookup cost: 0
Included by whitehouse.gov

TXT Record

v=spf1 ip4:198.2.128.0/24 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.145.0/24 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.177.0/24 ip4:198.2.178.0/23 ip4:198.2.180.0/24 ~all

Processed recursively per RFC 7208

0

TLS Security

0 / 10 points

Score Breakdown

TLS-RPT record configured (optional)
0 / 5
MTA-STS policy configured (optional)
0 / 5

TLS-RPT (Reporting)

TLS-RPT Not Configured

Publish a TXT record at _smtp._tls.whitehouse.gov with v=TLSRPTv1 and reporting URI (rua=).

MTA-STS (Policy)

MTA-STS Not Configured

Publish a TXT record at _mta-sts.whitehouse.gov with v=STSv1 and policy ID (id=).

Know when your DNS records change

The check you just ran shows your current configuration. But DNS records change, sometimes without you knowing. A well-meaning IT change, a third-party provider update, or an unauthorized modification can break your email delivery overnight.

Configuration Drift

IT changes that accidentally break authentication

Provider Updates

Third-party services changing their SPF includes

Unauthorized Changes

Attackers modifying records to send as you

DMARCTrust monitors your DNS records continuously. When something changes, you get an email alert with exactly what changed and why it matters. No more surprises when customers complain their emails bounced.

Start Monitoring

Check Another Domain

Run a free email authentication check (DMARC, SPF, BIMI).

We will generate a shareable URL for your domain.

Try popular examples: google.com, amazon.com, booking.com

Explore other domains

Discover how other organizations configure their email authentication

Popular Domains

Frequently checked

Well-Configured

Reject policy + valid SPF

Same Policy

Also using reject

Showing domains checked by our users. All data is from public DNS records.

About This Checker

What we check

We analyze your domain's email authentication: DMARC policy and alignment, SPF record and includes, and BIMI logo and certificate status when present.

Why it matters

Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF/DKIM from senders.

Included features

  • DMARC syntax, policy, and reporting validation
  • SPF record evaluation and include analysis
  • DKIM/SPF alignment interpretation
  • BIMI record and VMC detection
  • Clear setup and remediation guidance

Related Tools

Free DMARC Record Generator
State of DMARC: Top 100 Domains
Check Another Domain

Monitor your email authentication 24/7

This check shows a snapshot. With DMARCTrust, you get continuous monitoring of your DMARC reports and DNS records, with instant alerts when something changes.

Start Monitoring Now View Plans