What do your domain’s records actually say?
Every domain publishes its settings for anyone to read. This check reads them back to you in plain language — where the site points, who runs the DNS, and whether the records that keep your email out of spam are in place.
Check a domain
The lookup runs inside your browser against a public DNS resolver. Nothing is sent to this website, and the records it reads are public — anyone on the internet can read the same ones about any domain, including yours.
The six things we read
A and AAAA
The addresses a browser goes to. No A record means visitors have nowhere to land, even though the domain exists.
NS
Which nameservers answer for the domain. This is the one to check first when a change you made has not taken effect — a change made in the wrong place changes nothing.
MX
Where mail addressed to the domain should be delivered. No MX record means mail sent to your address has nowhere to go.
SPF
Lists which systems are allowed to send mail for the domain. It authenticates the envelope sender the receiving server sees, which is not the same as the From address a person reads.
DKIM
A signature on the message itself, checked against a key published in your DNS. The key sits under a selector name chosen by whoever set up the mail, so a check like this can only look for the common names.
DMARC
Tells receivers what to do when a message claiming your domain fails both SPF and DKIM, and asks for reports so you can see who is sending as you.
The problems this turns up most
No DMARC at all
Very common. SPF and DKIM are set up, nothing joins them together, and nobody ever sees the reports that would show the domain being used by someone else.
Two SPF records
Often the result of adding a second mail service without editing the first record. The specification treats two records as a permanent error, so the effect is not two rules — it is a domain whose SPF no longer works.
An SPF record ending in +all
Authorises every sender on the internet. It looks configured, which is worse than being empty.
DMARC left on p=none for years
Reports are collected and nothing is enforced. That is the correct way to start and a poor place to stop.
Website and mail moved together by mistake
Changing a host without carrying the MX records across takes the email down along with the site. This is the single most expensive DNS mistake we get called about.
Where this check stops
It reads what is published, and only that. It cannot tell you whether your mailbox passwords are sound, whether a listed sender is one you still use, or whether a DKIM key matches the one your mail server actually signs with. A selector we cannot guess is not a missing DKIM key — it only means we could not find it by name.
DNS answers are also cached all over the internet. A change made an hour ago may not show here yet, and that delay is normal rather than a fault.
If the report raises something, the fix belongs with whoever holds the DNS. We are happy to do it, and equally happy for your existing provider to — see hosting solutions, which covers business email.
Frequently asked questions
Is it legal to look up someone else’s domain?
These records are published deliberately so that any mail server or browser on the internet can read them. Reading them is how the internet works.
Do you store what I check?
No. The lookup goes from your browser to a public resolver. This site’s server never sees it.
Why does it say no DKIM when we have DKIM?
Because the selector is a name your mail provider chose and we can only try the common ones. The report says this rather than claiming DKIM is missing.
Our mail goes to spam. Will this tell me why?
It will tell you whether the authentication records are the cause, which they usually are. It cannot see content filtering, sending reputation or whether a recipient’s server simply does not like the sending IP.
We just changed our records. Why is the old one showing?
Caching. Records carry a time-to-live, and resolvers keep the old answer until it expires. Check again later.
Can you fix what it finds?
Yes, if you want us to. Tell us what the report said and who holds your DNS.
Send us what the report said
If something came back marked as a problem, tell us what it was and who your domain and email are with. We will tell you what needs changing and what it takes to change it — whether or not you move anything to us.