Quick access

Saved in this browser. Sign in to keep it on all your devices.

DNS Lookup

Check a domain’s A, AAAA, CNAME, MX, NS, TXT, SOA, and CAA records with their TTLs, and see at a glance whether its email is protected by SPF and DMARC. Answers come fresh from Google Public DNS.

You can paste a full web address or an email address; we use just the domain.

Version 1.1 Updated What's new

Release notes

  1. v1.1 Latest
    • Added an in-depth guide below the tool, written from what the tool actually does.

About the DNS Lookup

DNS turns domain names into the addresses and settings computers use. A lookup shows a domain’s records: where its website is (A), where its email goes (MX), and its verification entries (TXT).

How to use it

  1. 1 Enter a domain name, such as example.com, or paste a web or email address.
  2. 2 Read the email and security summary: MX, SPF, DMARC, CAA, and DNSSEC.
  3. 3 Review every record and its TTL, or copy them in zone-file format.

Frequently asked questions

How long do DNS changes take?

Usually minutes to a few hours, depending on the record’s TTL. Old values can stay cached until the TTL runs out.

What are MX records?

MX records name the mail servers that receive email for a domain, with a priority number. The lowest number is tried first.

What are TXT records used for?

For domain verification and email security, including SPF, DKIM, and DMARC records.

Why do I see different results from my own computer?

Your computer and ISP cache answers until the TTL runs out. This tool asks Google Public DNS fresh each time, so it shows the current records sooner after a change.

What should my DMARC policy be?

Start with p=none to collect reports, then move to p=quarantine and finally p=reject once only your own servers send mail. Gmail and Yahoo require a DMARC record from bulk senders.

What each record in the table does

  • A and AAAA: the IPv4 and IPv6 addresses of the server that answers for the name. Browsers connect here.
  • CNAME: an alias. www.example.com may point to example.netlify.app, and the A records then belong to that target.
  • MX: the mail servers that accept email for the domain. The number before each server is its priority; lower is tried first.
  • NS: the name servers that hold the domain’s records. They show which DNS provider is in charge.
  • TXT: free text, used for SPF, DMARC, and proof of ownership for Google, Microsoft and other services.
  • SOA: the zone’s administrative record, with its primary name server and serial number.
  • CAA: which certificate authorities may issue SSL certificates for the domain.

A record type missing from the table is listed underneath, so you can tell “not set” apart from “not checked”.

TTL and why a change takes time to show

Every answer carries a TTL, the number of seconds other resolvers may keep it in their cache. With a TTL of 3600, a resolver that looked the name up a minute before your change keeps serving the old value for up to an hour. That delay is what people call DNS propagation; nothing is actually sent around the internet.

This tool asks Google Public DNS, which picks up a change once any cached copy expires. Your own computer, router and internet provider keep their own caches, so they can lag behind. When planning a move to a new server, lower the TTL to 300 a day ahead, make the switch, then raise it again.

Reading the email and security checks

The summary at the top looks at the records that decide whether the domain’s email is trusted:

  • SPF lists the servers allowed to send mail for the domain. It should end in -all (reject the rest) or ~all (mark the rest as suspicious). +all lets anyone send as you, and two separate SPF records count as an error.
  • SPF may use at most 10 DNS lookups, counting each include:, a, mx and redirect. Every email service you add brings its own include:, so busy domains go over the limit and fail checks at random.
  • DMARC tells receivers what to do with mail that fails SPF and DKIM. p=none only collects reports, p=quarantine sends failures to spam and p=reject refuses them.
  • CAA, when set, names the only certificate authorities allowed to issue certificates. Without it any authority may.
  • DNSSEC signs the answers so they cannot be forged on the way to the resolver.

DKIM keys are not in the list because they sit under a selector name chosen by each email provider, such as google._domainkey, which cannot be guessed from the domain alone.

Fixing common DNS problems

  • Site still shows the old host: compare the A records here with the IP your new host gave you. If they match, the old address is cached on your side and will clear when the TTL runs out.
  • Email stopped arriving: check that the MX records point to your current mail provider and that no old MX entry is left with a lower number.
  • Your mail lands in spam: add the missing SPF or DMARC record and keep SPF under the lookup limit.
  • A certificate will not issue: a CAA record may list a different authority. Add the one your host uses, such as letsencrypt.org.
  • No records at all and a “doesn’t exist” message: the domain has expired or was never registered. The WHOIS lookup shows its status and dates.

The zone-file view gives every record in the standard BIND format, which most DNS hosts can import. It is a quick way to back up the records before you move the domain to another provider.