Live network utility
Run a practical DNS lookup for a domain and inspect the records that usually matter when a website, email setup, SSL certificate or migration is not behaving as expected. The tool checks web records, mail records, nameservers, TXT policy records, CAA, TTLs and a public resolver comparison.
The site resolver is used first. Google Public DNS is used for comparison and as a fallback when a record type is slow or unavailable.
Why DNS lookup is still the first check
DNS is the address book behind a domain. It decides where the website points, which mail servers accept incoming email, which provider controls the zone, which TXT records prove ownership, and which certificate authorities may issue SSL certificates. When a site migration, email setup or SSL renewal goes wrong, DNS is often the first layer worth checking because every other service depends on it.
A good DNS lookup should not stop at one A record. A website can resolve correctly while email is broken. Email can work while SPF or DMARC is missing. Nameservers can be delegated to the wrong provider even if an old cached answer still appears to work. Looking at several record types together gives a much more useful picture than checking them one by one.
What the main DNS records mean
- A records point a hostname to IPv4 addresses.
- AAAA records point a hostname to IPv6 addresses.
- CNAME records alias one hostname to another hostname.
- MX records tell other mail servers where to deliver email.
- NS records show the nameservers responsible for the domain.
- TXT records often contain SPF, verification tokens and other policies.
- SOA records describe the authority, serial and timing values for the zone.
- CAA records restrict which certificate authorities can issue certificates.
How to use the DNS report
Start with the summary. If A or AAAA records are missing, the website may not resolve as expected. If NS records look wrong, you may be editing DNS in the wrong control panel. If MX is missing, the domain may not receive email. If SPF or DMARC is absent, outbound email can be easier to spoof and more likely to land in spam. CAA is optional, but it is useful for locking down certificate issuance on production domains.
DNS changes and propagation
DNS changes are not always instant. TTL values tell resolvers how long they may cache an answer. A low TTL can help during migrations, but the old value may still be cached elsewhere. If a public resolver and your hosting panel disagree, wait for the previous TTL window and confirm that you are editing the authoritative nameservers.
Common questions
Why does my DNS lookup show old values?
Some resolvers may still have cached answers. Check the TTL and compare with the authoritative DNS provider before assuming the change failed.
Do I need both A and AAAA records?
No, but dual-stack IPv4 and IPv6 can improve reachability. Only add AAAA records when the server is actually configured to answer correctly over IPv6.
Why is DMARC checked separately?
DMARC is normally stored at _dmarc.yourdomain.com, not directly on the root domain. That is why this tool checks the root TXT records and the dedicated DMARC hostname.
What is the difference between an A and a CNAME record?
An A record points a name directly to an IPv4 address (AAAA for IPv6). A CNAME points one name to another name, which is then resolved. You cannot use a CNAME at a zone apex.
Why have my DNS changes not taken effect yet?
Resolvers cache records for the duration of their TTL. Until that TTL expires, clients keep serving the old value. Lower the TTL before a planned change to speed up propagation.
What does the MX record control?
MX records tell other mail servers where to deliver email for your domain, in priority order. Without a correct MX, inbound mail fails or bounces.
