Check your email DNS records
The four records that decide whether your mail lands in the inbox or the spam folder — checked in one go, with the finding explained rather than just printed.
- Runs from your browser, not our server
- No sign-up
- No watermark
Loading the tool…
How it works
- Enter your domain.
- Enter the DKIM selector if you know it (google, selector1, s1…).
- Read each block: the record itself, and what it means.
Why nothing is uploaded
Every operation on this page is done by code running inside your browser tab, using the same engine that renders web pages. The file is read from disk into your tab’s memory, transformed there, and written back out as a download. It is never sent anywhere — not to us, not to a third party.
Verify it yourself
- Open your browser’s developer tools (F12) and select the Network tab.
- Load your file and run the tool.
- The only requests you will see are the tool’s own code and, once cached, none at all.
Frequently asked questions
I have SPF but mail still goes to spam.
SPF alone proves little to a modern receiver. Without DMARC there is no policy tying the SPF result to the visible From address, so a forged sender can pass SPF for its own domain and still appear to be you. SPF, DKIM and DMARC are a set; two of the three is a gap.
Why do I have to know the DKIM selector?
Because DNS offers no way to list what exists under a name — you can only ask about a name you already know. The selector is chosen by whoever sends your mail, and it appears in the DKIM-Signature header of any message you have sent, as s=.
What should the DMARC policy be?
Start at p=none and read the reports for a few weeks; that tells you what is sending as you. Then move to quarantine, then reject. Jumping straight to reject with an unknown sender in the wild means silently losing real mail.