DNS troubleshooting

Run A DNS Lookup

Check common DNS records for a domain in one place and use the result as a fast starting point for debugging routing, mail, and verification issues.

Lookup focus

All common records

Checks A, AAAA, CNAME, MX, TXT, and NS records from the same backend utility stack.

Enter a domain or subdomain such as example.com or api.example.com.

Enter a domain like example.com to inspect its DNS records.

Why run a DNS lookup?

A DNS lookup helps you confirm how a domain is configured before you dig into deeper network issues. It is useful when a website is not resolving, email delivery looks wrong, or you need to verify that a recent DNS change is actually visible.

Use this page when you need to:

Verify whether a domain points to the expected IP addresses or aliases.

Check whether email or verification records appear to be present.

Confirm that a subdomain is returning the DNS data you expect before deeper debugging.

What this tool checks

This page returns a practical set of common DNS records in a single lookup. That makes it a good first stop when you want to verify web routing, mail configuration, domain ownership records, or which name servers appear to be responsible for the zone.

Why DNS matters before anything else

A surprising number of outages and setup issues start with DNS rather than the application itself. If the wrong record is published, a record is missing, or a subdomain points somewhere unexpected, the app can look broken even when the server is healthy. A quick lookup helps narrow that down fast.

How to read the results

Treat the lookup as a configuration snapshot. Look for obvious mismatches first: missing A records, unexpected CNAME targets, missing MX records for a mail domain, or TXT records that do not match the value your provider expects. Once the DNS shape looks right, move on to ping or application-level checks.