A and AAAA
Confirm the domain points to the expected IPv4 and IPv6 addresses before changing web or CDN routing.
DNS diagnostics
DNS Lookup Tool
Check A, AAAA, CNAME, MX, NS, TXT, and SOA records with a clean result view. Use it to verify new records, troubleshoot mail delivery, and confirm nameserver changes.
DoH lookupUses DNS-over-HTTPS for reliable browser-based queries.
Record filtersShow only the DNS record family you need.
TTL visibilitySee cache timing beside each returned answer.
Run a DNS lookup
Choose a record type, enter a domain, and review the grouped answers below.
Start a DNS lookup
Enter a domain above and click Search to see DNS records here.
What to check in DNS results
MX and TXT
Mail problems often come from missing MX records or incorrect SPF, DKIM, and DMARC TXT values.
NS and SOA
Nameserver and SOA records help identify who is authoritative and whether zone metadata looks current.
IP geolocation lookup
After checking A or AAAA records, use the IP geolocation lookup to review approximate location, ASN, and organization details.
DNS Troubleshooting Workflow
Start with the record type that matches the symptom. If a website is not loading, check A, AAAA, and CNAME records. If email is failing, check MX records and TXT records for SPF, DKIM, and DMARC. If new records are not appearing, compare TTL values and nameserver records to confirm whether the authoritative zone has changed or a resolver is still using cached data.
DNS issues often look like application problems. A browser error, mail bounce, failed certificate validation, or CDN misroute may begin with a missing record, an old CNAME, an incorrect MX priority, or a TXT record copied with extra spaces. Use the lookup result with device tests such as nslookup, dig, ping, and traceroute to separate name resolution from network reachability.
When changing records, note the old value, the new value, and the TTL before the change. Lowering TTL in advance can make planned migrations smoother, while checking NS and SOA records helps confirm that you are editing the correct authoritative DNS zone.
If a result looks wrong, test from more than one resolver and compare with the authoritative nameserver. Public resolvers can cache older answers, while an authoritative query shows what the zone currently publishes. This is especially useful during website moves, mail migrations, CDN onboarding, and certificate validation checks.