toolqik

213 · Network

DNS Lookup

A, AAAA, MX, TXT, NS, CNAME, SOA, CAA and SRV records.

Uses server

About this tool

DNS (the Domain Name System) turns a name like example.com into the addresses and settings the internet needs: which server hosts the website, which servers receive its email, and which services it has verified. This DNS lookup tool queries a domain’s public records so you can check them without a terminal.

How to use it

  1. Type a domain name. You can paste a full URL; the tool keeps just the host name.
  2. Tick the record types you need. A, AAAA, MX, NS and TXT are selected by default.
  3. Click Look up. Each record type you ticked shows its current values, or tells you none exist.

DNS record types explained

TypeWhat it doesTypical use
APoints a name to an IPv4 addressYour website’s server, e.g. 76.76.21.21
AAAAPoints a name to an IPv6 addressThe IPv6 version of the above
CNAMEMakes a name an alias of another namewww → cname.vercel-dns.com
MXMail servers for the domain, with prioritiesGoogle Workspace, Microsoft 365, Zoho Mail
NSThe name servers that are authoritative for the domainChecking which DNS provider is in charge
TXTFree-form textSPF, DKIM, DMARC, domain verification
SOAZone details: primary server, admin, serial number, timersConfirming a zone change was published
CAAWhich certificate authorities may issue certificatesRestricting SSL to e.g. Let’s Encrypt
SRVHost and port for a specific serviceSIP, XMPP, some Microsoft 365 records

Check SPF, DKIM and DMARC records

Email deliverability depends on three TXT records. Look them up like this:

  • SPF: TXT record on the domain itself, starting with v=spf1, e.g. v=spf1 include:_spf.google.com ~all. A domain should have only one SPF record.
  • DKIM: TXT record on selector._domainkey.example.com. The selector depends on your email provider (Google Workspace uses google by default).
  • DMARC: TXT record on _dmarc.example.com, starting with v=DMARC1, e.g. v=DMARC1; p=none; rua=mailto:dmarc@example.com.

Confirm a DNS change (propagation)

After you change a record, resolvers around the world keep the old answer until its TTL runs out. If your TTL was 3600, some users may see the old value for up to an hour. This tool shows what our server’s resolver sees right now, which is a quick check that the change is live at your DNS provider. If your own computer still shows the old value, its resolver or browser has it cached. To speed up future changes, lower the TTL (for example to 300) a day before you make them.

Common tasks

  • Connect a domain to a host (Vercel, Netlify, Cloudflare Pages, GitHub Pages): check the A record on the root domain and the CNAME on www match what the host asks for.
  • Verify domain ownership for Google Search Console or another service: look for its TXT record, such as google-site-verification=….
  • Move email providers: check that the MX records point to the new provider and that SPF includes it.
  • Find who manages a domain’s DNS: look up its NS records.

The same lookups from the command line

dig example.com A +short
dig example.com MX +short
dig _dmarc.example.com TXT +short
dig @1.1.1.1 example.com A      # ask a specific resolver

Privacy

Browsers can’t send DNS queries directly, so this tool asks our server to resolve the name. Only public domain names are accepted, and lookups are not logged.

FAQ

How do I check the DNS records of a domain?

Enter the domain above, choose the record types and click Look up. From a terminal, use dig example.com A on macOS or Linux, nslookup -type=A example.com, or Resolve-DnsName in PowerShell.

How do I check MX records?

Enter your domain and tick MX. The results list each mail server with its priority; lower numbers are tried first.

How do I look up a DMARC record?

Look up the TXT record of _dmarc.yourdomain.com. A valid record starts with v=DMARC1.

How long does DNS propagation take?

Usually minutes, but resolvers may keep the old answer until the record’s previous TTL expires, which is often up to an hour and occasionally up to 48 hours for name server changes.

Why do I see different results than my computer?

DNS answers are cached for the record’s TTL. Your local resolver may still hold an older answer while ours already sees the new one, or the other way round.

How do I check DKIM?

Query the TXT record of selector._domainkey.yourdomain.com, replacing "selector" with your provider’s DKIM selector.

Can I look up internal or local hostnames?

No. Only public domain names are allowed. Names like localhost, *.local or *.internal are rejected.

esc
↑↓ navigate↵ open