Free toolHisendy

Your records, read the way a receiving server reads them.

Put in a domain and it writes the three records you should publish, in the order you should publish them. Paste back what is live and it grades them the way Gmail does: lookup count, the qualifier on the end, key length, alignment. No lookup, no account, no waiting.

Free, runs in this tab

What you should publish

Three records, one at a time. DMARC last, and gently, or you will bin your own mail.

HostTypeValue
{{r.host}} {{r.type}} {{r.val}} {{r.why}}
DMARC, in three moves
{{stageWhy}}

Now paste what is actually live

{{g.t}}

{{f.label}} {{f.badge}}
Verdict
{{grade}}
Checks passed
{{passN}}/{{totalN}}
{{c.t}} {{c.d2}}

What a page in your browser cannot do for you.

Look your domain up A browser cannot ask a nameserver for a TXT record. So the checker reads what you paste from dig, from your registrar, or from the header of any mail you have sent. That is one copy and paste, and it keeps the page honest about where the answer came from.
See inside your DKIM key It reads the public half you publish: the version, the algorithm, whether the key is there at all, and roughly how long it is. It cannot tell you whether the private half still matches, which is what actually breaks after a provider migration.
Tell you the send will land These three records stop you being rejected outright. Whether you reach an inbox is about who you are writing to, how often, and whether they reply. That part is the product, not the DNS.
The other free tools
The Hisendy messenger

Records right. Pace still wrong.

Perfect authentication and forty cold emails on day one is still a burnt domain. Hisendy holds a new mailbox at 8 a day and walks it to 25.

Start free See the plans

No card. 2 mailboxes, 100 sends and 100 AI credits to start.