How these checks work together
MX shows where mail is routed. SPF lists authorized senders. DMARC defines receiver policy. Header analysis helps inspect what happened to one received message.
Check public mail DNS records and inspect pasted headers locally. These tools can surface SPF, DMARC, DKIM selector, MX, PTR, and Authentication-Results signals, but they do not prove complete deliverability or message safety.
Run a combined email authentication exposure estimate across MX, SPF, DMARC, DKIM selectors, PTR, MTA-STS, TLS-RPT, and selected sender-IP signals.
MX LookupFind mail exchanger hosts and priority.
SPF CheckerReview root-domain SPF TXT policy signals.
DMARC CheckerCheck _dmarc policy and reporting tags.
Email Header AnalyzerParse pasted headers locally for routing and auth signals.
DNS LookupInspect supporting TXT, MX, and selector records.
MX shows where mail is routed. SPF lists authorized senders. DMARC defines receiver policy. Header analysis helps inspect what happened to one received message.
No. They inspect DNS records or parse pasted headers locally.
No. Mailbox provider policy, reputation, DKIM selectors, and content can also matter.
No. The email header analyzer runs in the browser.
Check my email domain
Public mail-domain records and pasted email-header signals such as MX, SPF, DMARC, DKIM selector context, and sender-route clues.
Limits
It cannot guarantee inbox placement, inspect private mailboxes, or certify sender reputation everywhere.
Read results
Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.