Can someone send email pretending to be you?
Enter your domain. We check the DNS records that stop impersonation, and tell you in plain language what is missing. Nothing is stored and no signup is needed.
What these records actually do
Email was designed in an era when nobody expected the sender to lie. Three DNS records were bolted on afterwards to fix that, and most businesses have one of them half configured.
SPF
A list of the servers allowed to send mail using your domain. The most common failure is having two SPF records, usually because someone added a new one for a mail provider instead of editing the existing record. Two records is a hard failure, so SPF stops working entirely.
DKIM
A signature on every message, so a receiving server can prove the message came from you and was not modified. It survives forwarding, which SPF does not.
DMARC
The instruction. It tells receivers what to do when a message fails both SPF and DKIM: nothing, send it to junk, or reject it. It also sends you reports revealing who is sending mail as your domain, which is frequently an unpleasant surprise.
Why it matters commercially
Two reasons. Impersonation, where someone emails your client a fake invoice with changed banking details, which happens constantly in South Africa. And deliverability, because the same records decide whether your own invoices reach the inbox or the junk folder.
This tool reads public DNS records only. We do not store the domains you check, and we do not send you anything. DKIM is tested against 12 common selectors, so a custom selector may not be detected.