DNS Record Check and email health
You get the A, AAAA, CNAME, NS, MX, TXT and SOA records with their TTLs, and above all of them a separate check on the three records that decide whether your email reaches the inbox or the spam folder.
- No sign-up
- SPF and DMARC check
- TTL shown per record
Run the tool right here
All of a domain's DNS records, plus the SPF and DMARC checks that decide whether your email lands in spam.
- What it costs Free
- Data source Our own server
- Access No sign-up
The short answer
DNS records decide which server your domain name points to and where your email is allowed to be sent from. If your site emails land in spam, the cause is almost always a missing or wrongly written SPF or DMARC record.
SPF is the list of servers allowed to send mail on behalf of your domain. When that list does not exist, the receiving server has no way to tell whether a message claiming to be from info@ your site really came from there, so it does the most conservative thing and drops it into spam. DMARC goes one step further and tells the receiving server exactly what to do with a message that fails the test.
The second thing worth reading is the TTL, and nobody usually looks at it until it is too late. TTL is how many seconds DNS servers around the world hold on to the old answer. If you are about to move hosts, lower the TTL on the A record a day in advance; if you skip that, some of your visitors may still be hitting the old server hours after the move.
The NS record has a story of its own. Where your domain DNS is managed is not necessarily where the site is hosted, and on projects that several people have worked on those two have almost always drifted apart. When you change something in the hosting panel and nothing happens, the first right question is where this domain DNS actually lives.
Where the data comes from
A direct DNS query from our server. Note the answer may differ from what you see inside Iran, because some services return different answers to different IPs. We do not check DKIM here, because its selector depends on your mail service and without knowing the selector we cannot honestly say whether it exists.
When it helps
After a host migration, to confirm the records moved correctly. Or when your site's emails land in spam, which almost always means SPF or DMARC is missing.
Where it does not help
DKIM is not checked here, and that is deliberate. DKIM is read through a selector that depends on your email service, and without knowing that selector nobody can honestly say whether the record exists. Your own email service panel is where to look. The second limitation is technical: the lookup runs from our server, and some DNS services answer different IPs differently, so what you see here may not match what a visitor inside Iran gets.
One thing we learned using it
The most common SPF mistake is having two SPF records, not having none. A client adds a new email service, drops the new record next to the old one, and the standard says a domain with more than one SPF record fails the test. That is worse than before the setup. If you see two lines starting with v=spf1, they must be merged into one.
What it costs
This tool runs on our own server and we buy no data for it, so it is free and stays free. It only carries a daily cap so a bot cannot swallow the whole capacity.
The daily cap is counted per visitor. If you need more, a free account raises your limit.
Questions about this tool
How long does a DNS change take to apply?
It depends on that record TTL, not on a fixed number. Until then, servers that cached the previous answer keep serving it. That is why, before any planned change, you lower the TTL first and change the record afterwards.
What is the minimum correct setup so site email does not land in spam?
A correct MX record pointing at your real email service, an SPF record that authorises that same service, and a DMARC record even with a policy of none. The third one reports without blocking anything, and to start with that is enough.
Where is my domain DNS?
The NS records in this tool result answer that. Those names tell you which DNS service manages the domain, which is where you need to sign in to change a record.