English Deutsch Español Français Italiano Nederlands Polski Українська
Domain & DNS

DNS record lookup

Query A, AAAA, MX, TXT, NS, CNAME and SOA records.

Domain or IP Enter a domain. For PTR choose it as the only type and enter an IP.
Record types
PTR lives in the reverse (arpa) zone and cannot be combined with other record types.
Resolver
Try: example.com google.com cloudflare.com
Domain
cloudflare.com
Resolver?
Google (8.8.8.8)
Records
42
Query time
302.77 ms
A records (2)?
Host TTL? Value
cloudflare.com 300 104.16.133.229
cloudflare.com 300 104.16.132.229
AAAA records (2)?
Host TTL? Value
cloudflare.com 300 2606:4700::6810:85e5
cloudflare.com 300 2606:4700::6810:84e5
MX records (4)?
Host TTL? Value
cloudflare.com 897 5 mxa-canary.global.inbound.cf-emailsecurity.net
cloudflare.com 897 10 mxa.global.inbound.cf-emailsecurity.net
cloudflare.com 897 5 mxb-canary.global.inbound.cf-emailsecurity.net
cloudflare.com 897 10 mxb.global.inbound.cf-emailsecurity.net
TXT records (28)?
Host TTL? Value
cloudflare.com 300 stripe-verification=5096d01ff2cf194285dd51cae18f24fa9c26dc928cebac3636d462b4c6925623
cloudflare.com 300 logmein-verification-code=b3433c86-3823-4808-8a7e-58042469f654
cloudflare.com 300 miro-verification=bdd7dfa0a49adfb43ad6ddfaf797633246c07356
cloudflare.com 300 docker-verification=c578e21c-34fb-4474-9b90-d55ee4cba10c
cloudflare.com 300 facebook-domain-verification=h9mm6zopj6p2po54woa16m5bskm6oo
cloudflare.com 300 atlassian-domain-verification=WxxKyN9aLnjEsoOjUYI6T0bb5vcqmKzaIkC9Rx2QkNb751G3LL/cus8/ZDOgh8xB
cloudflare.com 300 google-site-verification=ZdlQZLBBAPkxeFTCM1rpiB_ibtGff_JF5KllNKwDR9I
cloudflare.com 300 _neqmkgaq1lq9it5s8qmetrhbnu121wb
cloudflare.com 300 databank-domain-verification-hkehd2=fzgu4kmbZwMoW99zENgO4u8NL
cloudflare.com 300 stripe-verification=bf1a94e6b16ace2502a4a7fff574a25c8a45291054960c883c59be39d1788db9
cloudflare.com 300 uber-domain-verification=58086039-150a-42a4-a4be-b4032921aa0f
cloudflare.com 300 apple-domain-verification=DNnWJoArJobFJKhJ
cloudflare.com 300 DirectFedAuthUrl=https://cloudflare-security.cloudflareaccess.com/cdn-cgi/access/sso/saml/ebec933773c69c93420d13e6776adb8c4a190f6281f9d132bcebd7dcb0967bdd
cloudflare.com 300 google-site-verification=C7thfNeXVahkVhniiqTI1iSVnElKR_kBBtnEHkeGDlo
cloudflare.com 300 status-page-domain-verification=r14frwljwbxs
cloudflare.com 300 canva-site-verification=oOyaVnHC-OiFoR1BPvetNA
cloudflare.com 300 liveramp-site-verification=EhH1MqgwbndTWl1AN64hOTKz7hc1s80yUpchLbgpfY0
cloudflare.com 300 _wkjc0fot0d7qrvrdt78bxkj2e2o67d2
cloudflare.com 300 drift-domain-verification=f037808a26ae8b25bc13b1f1f2b4c3e0f78c03e67f24cefdd4ec520efa8e719f
cloudflare.com 300 DirectFedAuthUrl=https://cloudflare-security.cloudflareaccess.com/cdn-cgi/access/sso/saml/dba6756ad312fc13c45f705cf7f5e87f4d658be016c41f950329aa4085b3abc1
cloudflare.com 300 creatopy-domain-verification=97d2ca50-9b6f-4a21-9bdb-fbb630e4cec7
cloudflare.com 300 onetrust-domain-verification=bd5cd08a1e9644799fdb98ed7d60c9cb
cloudflare.com 300 cisco-ci-domain-verification=27e926884619804ef987ae4aa1c4168f6b152ada84f4c8bfc74eb2bd2912ad72
cloudflare.com 300 ZOOM_verify_7LFBvOO9SIigypFG2xRlMA
cloudflare.com 300 MS=ms70274184
cloudflare.com 300 _saml-domain-challenge.2dc00405-79cd-457b-b288-a119c6f0c7b7.71996d53-d178-4ba9-bef4-7f7e46edab74.cloudflare.com=1c8736fd-84b2-4197-985f-3fb2852f2457
cloudflare.com 300 v=spf1 ip4:199.15.212.0/22 ip4:173.245.48.0/20 include:_spf.google.com include:spf1.mcsv.net include:spf.mandrillapp.com include:mail.zendesk.com include:stspg-customer.com include:_spf.salesforce.com -all
cloudflare.com 300 asv=894f6d1f9f83bcf44e4b1bc40bc1c4aa
NS records (5)?
Host TTL? Value
cloudflare.com 21600 ns4.cloudflare.com
cloudflare.com 21600 ns5.cloudflare.com
cloudflare.com 21600 ns6.cloudflare.com
cloudflare.com 21600 ns3.cloudflare.com
cloudflare.com 21600 ns7.cloudflare.com
SOA records (1)?
Host TTL? Value
cloudflare.com 187 ns3.cloudflare.com dns.cloudflare.com serial 2410308532
Raw Output
cloudflare.com.  300  IN  A  104.16.133.229
cloudflare.com.  300  IN  A  104.16.132.229
cloudflare.com.  300  IN  AAAA  2606:4700::6810:85e5
cloudflare.com.  300  IN  AAAA  2606:4700::6810:84e5
cloudflare.com.  897  IN  MX  5 mxa-canary.global.inbound.cf-emailsecurity.net.
cloudflare.com.  897  IN  MX  10 mxa.global.inbound.cf-emailsecurity.net.
cloudflare.com.  897  IN  MX  5 mxb-canary.global.inbound.cf-emailsecurity.net.
cloudflare.com.  897  IN  MX  10 mxb.global.inbound.cf-emailsecurity.net.
cloudflare.com.  300  IN  TXT  "stripe-verification=5096d01ff2cf194285dd51cae18f24fa9c26dc928cebac3636d462b4c6925623"
cloudflare.com.  300  IN  TXT  "logmein-verification-code=b3433c86-3823-4808-8a7e-58042469f654"
cloudflare.com.  300  IN  TXT  "miro-verification=bdd7dfa0a49adfb43ad6ddfaf797633246c07356"
cloudflare.com.  300  IN  TXT  "docker-verification=c578e21c-34fb-4474-9b90-d55ee4cba10c"
cloudflare.com.  300  IN  TXT  "facebook-domain-verification=h9mm6zopj6p2po54woa16m5bskm6oo"
cloudflare.com.  300  IN  TXT  "atlassian-domain-verification=WxxKyN9aLnjEsoOjUYI6T0bb5vcqmKzaIkC9Rx2QkNb751G3LL/cus8/ZDOgh8xB"
cloudflare.com.  300  IN  TXT  "google-site-verification=ZdlQZLBBAPkxeFTCM1rpiB_ibtGff_JF5KllNKwDR9I"
cloudflare.com.  300  IN  TXT  "_neqmkgaq1lq9it5s8qmetrhbnu121wb"
cloudflare.com.  300  IN  TXT  "databank-domain-verification-hkehd2=fzgu4kmbZwMoW99zENgO4u8NL"
cloudflare.com.  300  IN  TXT  "stripe-verification=bf1a94e6b16ace2502a4a7fff574a25c8a45291054960c883c59be39d1788db9"
cloudflare.com.  300  IN  TXT  "uber-domain-verification=58086039-150a-42a4-a4be-b4032921aa0f"
cloudflare.com.  300  IN  TXT  "apple-domain-verification=DNnWJoArJobFJKhJ"
cloudflare.com.  300  IN  TXT  "DirectFedAuthUrl=https://cloudflare-security.cloudflareaccess.com/cdn-cgi/access/sso/saml/ebec933773c69c93420d13e6776adb8c4a190f6281f9d132bcebd7dcb0967bdd"
cloudflare.com.  300  IN  TXT  "google-site-verification=C7thfNeXVahkVhniiqTI1iSVnElKR_kBBtnEHkeGDlo"
cloudflare.com.  300  IN  TXT  "status-page-domain-verification=r14frwljwbxs"
cloudflare.com.  300  IN  TXT  "canva-site-verification=oOyaVnHC-OiFoR1BPvetNA"
cloudflare.com.  300  IN  TXT  "liveramp-site-verification=EhH1MqgwbndTWl1AN64hOTKz7hc1s80yUpchLbgpfY0"
cloudflare.com.  300  IN  TXT  "_wkjc0fot0d7qrvrdt78bxkj2e2o67d2"
cloudflare.com.  300  IN  TXT  "drift-domain-verification=f037808a26ae8b25bc13b1f1f2b4c3e0f78c03e67f24cefdd4ec520efa8e719f"
cloudflare.com.  300  IN  TXT  "DirectFedAuthUrl=https://cloudflare-security.cloudflareaccess.com/cdn-cgi/access/sso/saml/dba6756ad312fc13c45f705cf7f5e87f4d658be016c41f950329aa4085b3abc1"
cloudflare.com.  300  IN  TXT  "creatopy-domain-verification=97d2ca50-9b6f-4a21-9bdb-fbb630e4cec7"
cloudflare.com.  300  IN  TXT  "onetrust-domain-verification=bd5cd08a1e9644799fdb98ed7d60c9cb"
cloudflare.com.  300  IN  TXT  "cisco-ci-domain-verification=27e926884619804ef987ae4aa1c4168f6b152ada84f4c8bfc74eb2bd2912ad72"
cloudflare.com.  300  IN  TXT  "ZOOM_verify_7LFBvOO9SIigypFG2xRlMA"
cloudflare.com.  300  IN  TXT  "MS=ms70274184"
cloudflare.com.  300  IN  TXT  "_saml-domain-challenge.2dc00405-79cd-457b-b288-a119c6f0c7b7.71996d53-d178-4ba9-bef4-7f7e46edab74.cloudflare.com=1c8736fd-84b2-4197-985f-3fb2852f2457"
cloudflare.com.  300  IN  TXT  "v=spf1 ip4:199.15.212.0/22 ip4:173.245.48.0/20 include:_spf.google.com include:spf1.mcsv.net include:spf.mandrillapp.com include:mail.zendesk.com include:stspg-customer.com include:_spf.salesforce.com -all"
cloudflare.com.  300  IN  TXT  "asv=894f6d1f9f83bcf44e4b1bc40bc1c4aa"
cloudflare.com.  21600  IN  NS  ns4.cloudflare.com.
cloudflare.com.  21600  IN  NS  ns5.cloudflare.com.
cloudflare.com.  21600  IN  NS  ns6.cloudflare.com.
cloudflare.com.  21600  IN  NS  ns3.cloudflare.com.
cloudflare.com.  21600  IN  NS  ns7.cloudflare.com.
cloudflare.com.  187  IN  SOA  ns3.cloudflare.com. dns.cloudflare.com. 2410308532 10000 2400 604800 300
What does each field mean?

Field reference

TTL

Seconds a downstream resolver is allowed to cache the record before re-asking the authoritative server. Short TTL (60–300) means changes propagate fast but every resolver hits you more often; long TTL (1h–1d) reduces load but slows DNS changes.

A record

Maps a hostname to a 32-bit IPv4 address (e.g., <code>example.com → 93.184.216.34</code>). Most common DNS record type; web traffic begins with an A lookup.

AAAA record

IPv6 equivalent of A — 128-bit address (e.g., <code>2606:2800:220:1::93:184:216:34</code>). Modern hosts publish both A and AAAA; the resolver picks one per the client's connectivity.

MX record

Lists the hostname(s) of mail exchangers plus a priority number — lowest priority is tried first. Without an MX, email cannot be delivered to the domain. Examples: <code>10 mail.example.com</code>.

CNAME

Canonical Name: tells the resolver "to find me, look up X instead". Cannot coexist with any other record on the same name and cannot exist at the zone apex (the bare domain). Useful for CDNs and SaaS providers.

TXT

Originally arbitrary text, today carries machine-readable policies: SPF (allowed mail senders), DKIM (signing keys), DMARC (email-auth policy), and domain-ownership tokens for Google/Microsoft/AWS.

NS

Lists the servers that hold the actual zone data. The TLD registry returns NS records during the referral chain; resolvers then ask these servers for everything else. Changing NS effectively re-delegates the domain.

PTR

Maps an IP back to a name. Required for mail servers — many providers reject SMTP from IPs with missing or generic PTR. The owner of the IP block (not the domain owner) controls PTR records.

SOA

Each zone has exactly one SOA: master NS, contact email, serial number (incremented on changes — secondaries use it to detect updates), refresh/retry/expire timers, default negative-cache TTL.

CAA

Certification Authority Authorization restricts which CAs may issue certificates for the domain. Example: <code>0 issue "letsencrypt.org"</code> blocks every CA except Let's Encrypt. CAs are required to honor CAA before issuance.

Resolver

Public recursive resolver we asked: Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9). Different resolvers may return different answers because of TTL races, anycast, or geo-targeted DNS.

About this tool

A DNS lookup asks an authoritative or recursive resolver what records a domain publishes. Our tool runs a live query against Google, Cloudflare, or Quad9 and shows you every record with its TTL — the same data dig prints on the command line, formatted for quick scanning.

You can pull the common record types on a single page: A and AAAA for hosts, MX for mail routing, TXT for SPF/DKIM/verification strings, NS for delegation, SOA for zone metadata, plus CNAME, SRV, CAA, and reverse PTR. Pick only the types you need to keep the answer compact.

When to use this tool

  • After a DNS change. Query multiple resolvers to confirm a new record is live before pointing traffic at it.
  • Debugging email deliverability. Inspect MX, SPF, DKIM, and DMARC records in one pass.
  • Verifying ownership. Pull the TXT record a third-party service asked you to publish.
  • Reverse DNS. Run a PTR query on an IP to find the hostname a mail server or logger will attribute to it.

Why you may see different answers

Public resolvers cache records for the TTL you configured at your authoritative nameserver. Google may still serve the old value while Cloudflare already shows the new one. Switch the resolver to compare — the TTL column tells you when the cache will expire. For a global view across 20+ vantage points, see the propagation check linked below.

Frequently asked questions

Which DNS resolver should I use?
All three (Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9 9.9.9.9) are public, anycasted, and return authoritative-sourced answers. Cloudflare tends to be the fastest; Quad9 filters known-malicious names; Google has the most predictable behaviour across regions. Switch between them to see whether an issue is global or resolver-specific.

What is the TTL column?
Time-to-live in seconds — how long a downstream resolver is allowed to cache this record. A low TTL (60–300s) means changes propagate quickly; a high TTL (3600–86400s) means the record is stable. If you are about to change a record, lower its TTL first and wait for the old TTL to elapse before cutting over.

Do you query the authoritative nameserver directly?
No — we query the public resolver you select, the same way a browser or mail server would. That is usually what you want: it matches what the rest of the internet sees. If you need to verify what the authoritative server currently publishes, use a +norecurse dig or a hosting-specific tool.

Why do PTR records look different?
A PTR lookup resolves an IP back to a hostname and uses the .in-addr.arpa (IPv4) or .ip6.arpa (IPv6) reverse zone. To avoid mixing record types that live in different zones, pick PTR on its own and enter an IP address instead of a domain.

Is the result cached?
We cache resolver answers for five minutes so repeated lookups against the same domain and resolver do not waste upstream query budget. If you need to force a fresh query, switch the resolver or wait out the five-minute window. Authoritative TTLs are reported unchanged — our cache only affects how often our backend re-queries.