Skip to content
XUtilHub

How to Check DNS Records for Any Domain

XUtilHub Team ·

DNS is the internet's address book. When a website won't load after a server move, or emails suddenly stop arriving, the answer is often in a DNS record. Here's what the main records do and how to check them.

The records that matter

RecordWhat it doesExample
APoints a name to an IPv4 addressexample.com → 93.184.215.14
AAAAPoints a name to an IPv6 addressexample.com → 2606:2800:21f::1
CNAMEMakes a name an alias of another namewww → example.com
MXSays which servers receive email10 mail.example.com
TXTHolds text: SPF, DKIM, DMARC, verification codesv=spf1 include:_spf.google.com ~all
NSNames the servers that hold the domain's DNSns1.cloudflare.com
CAASays which authorities may issue SSL certificates0 issue "letsencrypt.org"

How to look them up

Enter a domain in the DNS lookup tool. It queries public resolvers (Cloudflare, Google and Quad9) and shows every record type with its TTL, the number of seconds resolvers may cache the answer.

On a computer, you can also use the command line:

nslookup -type=MX example.com
dig example.com A

Troubleshooting common problems

Website not loading after moving hosts

  1. Check the A record shows the new server's IP.
  2. Check the NS records point to the DNS provider where you made the change. Editing records at your registrar does nothing if the domain uses Cloudflare's name servers, for example.
  3. Wait for the old TTL to expire. If it was 86400, that's up to 24 hours.

Emails not arriving

  1. Check there are MX records and that they point to your email provider.
  2. Check your SPF TXT record includes the services that send your email, and that DKIM and DMARC records are set up too.

www works but the bare domain doesn't (or the other way round)

Both need records. Typically the bare domain has an A record and www has a CNAME pointing to it.

SSL certificate won't issue

A CAA record may be restricting which certificate authorities can issue for your domain. Add one for your provider, or remove the restriction.

What is DNS propagation?

People say DNS changes "take 48 hours to propagate". Really, resolvers around the world keep their cached copy until its TTL expires. Lower the TTL to 300 seconds a day before a planned change, and the switch-over will take minutes instead of hours.

Who owns the domain?

DNS tells you where a domain points; WHOIS tells you who registered it and when it expires. Use the WHOIS lookup, and check the HTTPS setup with the SSL checker.

Tools mentioned in this article

← All articles