MailAuth LabWorked baseline: example.com authentication DNS
Open the live tool with ?d=example.com — this page documents what empty or minimal records mean.
- Share Url
- /email-auth-checker/?d=example.com
- Expect Mx
- IANA example.com may show mail exchangers; treat live output as source of truth
- Expect Spf
- Often v=spf1 -all on reserved domains — still verify live
- Expect Dmarc
- May be absent — checker should fail or warn until published
Use example.com as a safe domain to click through the UI. The shareable tool URL is /email-auth-checker/?d=example.com; the page updates the query with history.replaceState and does not full-reload.
If MX is missing, the domain is not configured to receive mail at the DNS layer. If SPF is missing, many receivers have no policy for which IPs may send. If DMARC is missing, there is no domain-owner policy for failed authentication.
When you move to your real domain, leave the DKIM selector blank first to probe common names (default, google, selector1, selector2, and others). If nothing matches, paste the s= value from a real message header.
Pro monitoring (multi-domain schedules, DMARC report inbox digests, alerts, history, API) is listed on the subscribe page as a mailto interest list only — this free site stays zero-backend.
Again: findings are for discovery and remediation drafting, not a promise of inbox placement.