- Home
- Domain, DNS and IP
- DNS Lookup
DNS Lookup
See how a domain is actually configured — addressing, mail, and verification records.
Queried live from public resolvers. Results reflect what is currently cached and served, which is what visitors and mail servers actually see — not necessarily what is written in your control panel, if a change is still propagating. No usage limit.
What this tool is for
DNS is the layer that turns a name into an address, and it quietly decides far more than that. Where the site is hosted, where email is delivered, which services are allowed to send on your behalf, which providers have proven they own the domain — all of it lives in a handful of records most people never look at.
Which is why DNS is behind so many mysterious failures. Email arriving in spam. A site that resolves for some visitors and not others. A subdomain still pointing at a provider you left two years ago. None of these announce themselves as DNS problems.
This lookup shows the current configuration as resolvers report it — the state that actually applies, which is not always the state in your control panel while a change propagates.
How to read your results
The A and AAAA records give the IPv4 and IPv6 addresses serving the domain. Two different addresses for the bare domain and www is normal; two different addresses that belong to two different hosting providers usually means a migration was never finished.
The MX records route email, in priority order, lowest number first. If you use a mail provider, these should point at that provider and nowhere else. An MX record pointing at your web host while you use a separate mail service is a classic cause of silently lost mail.
The TXT records carry authentication. Exactly one SPF record starting
v=spf1 — two SPF records invalidate each other, which is worse than none.
A DMARC record on _dmarc sets policy. Since 2024, bulk senders without these
are filtered aggressively by Gmail and Yahoo.
The TTL is how long each answer may be cached. It is the number that governs migrations: whatever you set is how long the old value can persist somewhere in the world after you change it.
The most common mistakes
Migrating without lowering the TTL first. Change the records with a TTL of 86400 and some visitors reach the old server for a full day. Drop it to 300 twenty-four hours before the move and the switch takes minutes.
Publishing two SPF records. The specification allows exactly one. A second record — typically added when a new mailing service is set up — makes both invalid, and mail that used to arrive starts failing authentication. Merge them into a single record instead.
Deleting TXT records that look meaningless. Verification strings are deliberately opaque. Removing one can invalidate ownership of a service, break single sign-on, or disable mail authentication, often weeks later when something re-checks.
Leaving a subdomain pointing at a service you no longer use. A dangling CNAME to an abandoned platform can be claimed by someone else, who then serves content from your domain. This is subdomain takeover, and it is fully automated by attackers.
Testing only from your own machine. Your computer and your router both cache DNS. A change can appear broken locally while working everywhere else, or the reverse. Checking from an independent resolver removes that doubt.
Related tools
- Whois Lookup Registration, expiry and ownership details of a domain name
- SSL Certificate Checker Validity, chain of trust and expiry date of a certificate
- Redirect Checker Follow the full redirect chain of a URL, hop by hop
- Meta Tags Analyzer Title, description, Open Graph and indexing directives of a page
Frequently asked questions
How long does a DNS change take?
The TTL of the record decides, not your provider. A record with a TTL of 3600 can be cached for an hour by every resolver that already asked. Before a planned migration, lower the TTL to 300 a day in advance, migrate, then raise it again — this turns a day of uncertainty into five minutes.
What is the difference between an A record and a CNAME?
An A record points a name directly at an IP address. A CNAME points a name at another name, which is then resolved in turn. CNAME is convenient when the target IP changes often, but it cannot be used at the root of a domain — a limitation that surprises people setting up example.com rather than www.example.com.
Why do I need SPF, DKIM and DMARC?
Because without them anyone can send email that appears to come from your domain, and because Gmail and Yahoo have required authentication from bulk senders since February 2024. Missing records no longer mean a slightly lower reputation — they increasingly mean delivery to spam or outright rejection.
Can I have several MX records?
Yes, and you should. Each carries a priority number, lowest first. A second MX record pointing at a backup server means mail queues instead of bouncing when the primary is unreachable. Two records with the same priority share the load rather than providing failover.
What is a TXT record for?
Originally free-form notes; in practice it now carries most verification and policy data — SPF, DKIM, DMARC, and ownership proofs for Google, Microsoft and others. It is normal for a working domain to have several, and removing one you do not recognise is a common way to break email or lock yourself out of a service.
Why do results differ between tools?
Caching. Each resolver holds its own copy until the TTL expires, so a change propagates unevenly across the internet for as long as the TTL allows. Two tools querying different resolvers can legitimately disagree for hours. Neither is wrong; both are reporting what they were told.