Specialist check
Receiver requirements checker for cold email
Check the public authentication records and optional message-header evidence that receiver requirements depend on before a campaign launches.
- Checks
- Combines public DNS with optional locally parsed headers from a real test message.
- Cannot tell
- It cannot observe complaint rates, live SMTP transport, message body rendering, or inbox placement.
Expected time: about 5 to 20 seconds. Some public services can take longer.
Source: Live Google Public DNS plus local header parsing. Pasted headers never leave this browser.
Questions
It checks public SPF, DKIM, DMARC, and MX evidence for one domain. If you paste headers from a real message, it also reads authentication results, DMARC alignment evidence, and one-click unsubscribe headers.
DNS shows that records are published. Headers show what a real sender path reported for SPF, DKIM, DMARC, and unsubscribe handling. Paste headers when you have already sent a test message from the campaign setup.
No. It checks observable setup evidence. Receiver decisions also depend on volume, complaints, message content, list quality, sending history, and signals that a browser tool cannot inspect.
Marketing and promotional messages are checked for RFC 8058 one-click unsubscribe headers. Transactional messages show that row as not scored, but the other authentication checks still apply.
Related checks