DNS records decide where your website loads from and where your email goes. When something breaks after a change, checking the records is the fastest way to find the cause.
How to check DNS records
- Open our free DNS lookup tool.
- Enter the domain, for example example.com.
- Choose "All records" or a single type, then click Lookup.
What each record type means
| Type | Purpose | Example value |
|---|---|---|
| A | IPv4 address of the website | 203.0.113.10 |
| AAAA | IPv6 address | 2001:db8::1 |
| CNAME | Alias to another name | www points to example.com |
| MX | Mail servers and priority | 10 mail.example.com |
| NS | Nameservers for the domain | ns1.example.net |
| TXT | SPF, DKIM, DMARC, verification | v=spf1 ... |
| SOA | Zone information and serial number | serial 2024010101 |
| CAA | Which CAs may issue SSL | 0 issue "letsencrypt.org" |
Common problems you can spot
- Website opens an old server: the A record still has the old IP address.
- "www" does not work: there is no CNAME or A record for www.
- Email bounces or is missing: MX records are missing, wrong or point to a server that does not exist.
- Email goes to spam: SPF, DKIM or DMARC TXT records are absent. See SPF, DKIM and DMARC explained.
- CNAME conflict: a CNAME cannot coexist with other records on the same name.
Why results can differ from what you set
DNS answers are cached. If you changed a record recently, some resolvers still return the old value until the TTL expires. Learn more in how long DNS propagation takes. To see what the domain's own servers publish, use the nameserver checker.
Best practices
- Lower the TTL a day before a planned change.
- Change one thing at a time and re-check.
- Document your records before editing.
- Do not delete MX records unless you are sure email is not needed.
Reading a real example
Imagine a lookup for acme-traders.com returns: an A record 203.0.113.5, a CNAME for www pointing to acme-traders.com, two MX records (priority 10 and 20), two NS records and a TXT record starting with v=spf1. This tells you the website lives on 203.0.113.5, email is handled by the MX hosts, and an SPF policy exists. If a customer reports that email is bouncing, the MX and SPF lines are where you look first.
A checklist after moving hosting
- The A record matches the new server's IP address.
- The www record resolves to the same place.
- MX records still point to your email provider.
- SPF and DKIM TXT records were copied across.
- Nameservers match the ones your host gave you.
Tips from the field
- Take a screenshot or export of all records before touching anything.
- If you see unexpected records, find out who added them before deleting.
- TXT records for verification (Google, Microsoft, social platforms) are safe to leave in place.
FAQ
Can I edit DNS records with this tool?
No. The tool only reads records. Edit them at your DNS host, such as cPanel's Zone Editor if you use our nameservers. See how to add DNS records.
Why are there several A records?
Some sites use several servers for load balancing or a CDN. Visitors may receive any of them.
Try it now: use our free WHOIS lookup, DNS lookup, nameserver checker, SSL checker and IP & hosting lookup. All free, no signup.