Domain & DNS

Check Your DNS Records

Look up A, AAAA, CNAME, MX, NS and TXT records for any domain.

Problem: Your domain isn't connecting correctly to your website or email.

We query public DNS over HTTPS and return the records currently published for your domain, so you can confirm your website and email are pointing where you expect.

Free. No account required.

What we'll check

  • A and AAAA records (website hosting)
  • CNAME aliases
  • MX records (email routing)
  • NS records (authoritative nameservers)
  • TXT records (SPF, verification)
  • CAA records where present

What each record does

  • A / AAAA — maps your domain to the IPv4 / IPv6 address of your web server.
  • CNAME — points one hostname at another, commonly for www or a CDN.
  • MX — tells other mail servers where to deliver your email.
  • NS — names the authoritative nameservers; if these are wrong nothing else applies.
  • TXT — holds SPF, DKIM and domain-verification strings.
  • CAA — restricts which certificate authorities may issue certificates for the domain.

Common DNS problems

  • Nameservers still pointing at an old host after a migration.
  • An A record left on a decommissioned server's IP.
  • www resolving but the apex domain not, or the reverse.
  • MX records removed during a website migration, silently killing email.
  • Multiple SPF TXT records, which invalidates SPF entirely.
  • Very long TTLs slowing propagation of a fix.

How DNS propagation works

Resolvers cache answers for the record's TTL. After a change, some networks still serve the old value until that cache expires. Lower the TTL before a planned migration, and expect up to 48 hours for stragglers otherwise.

Frequently asked questions

Why do I see different DNS results elsewhere?
Resolvers cache independently. Differences usually mean a recent change that has not fully propagated.
How long do DNS changes take?
Usually minutes to a few hours, bounded by the record's TTL. Nameserver changes at the registrar can take longer.
Can I have two SPF records?
No. A domain must publish exactly one SPF TXT record; merge multiple senders into a single record using include statements.

More tools