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

DNS-record-opzoeking

Bevraag A-, AAAA-, MX-, TXT-, NS-, CNAME- en 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
google.com
Resolver?
Google (8.8.8.8)
Records
31
Query time
344.43 ms
A records (6)?
Host TTL? Value
google.com 300 142.251.14.139
google.com 300 142.251.14.100
google.com 300 142.251.14.138
google.com 300 142.251.14.102
google.com 300 142.251.14.113
google.com 300 142.251.14.101
AAAA records (4)?
Host TTL? Value
google.com 300 2a00:1450:4001:c15::65
google.com 300 2a00:1450:4001:c15::8b
google.com 300 2a00:1450:4001:c15::8a
google.com 300 2a00:1450:4001:c15::66
MX records (1)?
Host TTL? Value
google.com 115 10 smtp.google.com
TXT records (15)?
Host TTL? Value
google.com 300 globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8=
google.com 300 docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e
google.com 300 facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
google.com 300 docusign=1b0a6754-49b1-4db5-8540-d2c12664b289
google.com 300 google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ
google.com 300 v=spf1 include:_spf.google.com ~all
google.com 300 MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB
google.com 300 google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0
google.com 300 apple-domain-verification=30afIBcvSuDV2PLX
google.com 300 onetrust-domain-verification=0d477fe608074e6f9c12bca7826035cc
google.com 300 cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b
google.com 300 Z29vZ2xl
google.com 300 onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0
google.com 300 google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o
google.com 300 work-accounts-domain-verification=Tcj6JjIMZOw2KsSEw2Nt2rLae89tN6
NS records (4)?
Host TTL? Value
google.com 21600 ns4.google.com
google.com 21600 ns1.google.com
google.com 21600 ns3.google.com
google.com 21600 ns2.google.com
SOA records (1)?
Host TTL? Value
google.com 29 ns1.google.com dns-admin.google.com serial 953810495
Raw Output
google.com.  300  IN  A  142.251.14.139
google.com.  300  IN  A  142.251.14.100
google.com.  300  IN  A  142.251.14.138
google.com.  300  IN  A  142.251.14.102
google.com.  300  IN  A  142.251.14.113
google.com.  300  IN  A  142.251.14.101
google.com.  300  IN  AAAA  2a00:1450:4001:c15::65
google.com.  300  IN  AAAA  2a00:1450:4001:c15::8b
google.com.  300  IN  AAAA  2a00:1450:4001:c15::8a
google.com.  300  IN  AAAA  2a00:1450:4001:c15::66
google.com.  115  IN  MX  10 smtp.google.com.
google.com.  300  IN  TXT  "globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8="
google.com.  300  IN  TXT  "docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e"
google.com.  300  IN  TXT  "facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95"
google.com.  300  IN  TXT  "docusign=1b0a6754-49b1-4db5-8540-d2c12664b289"
google.com.  300  IN  TXT  "google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ"
google.com.  300  IN  TXT  "v=spf1 include:_spf.google.com ~all"
google.com.  300  IN  TXT  "MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB"
google.com.  300  IN  TXT  "google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0"
google.com.  300  IN  TXT  "apple-domain-verification=30afIBcvSuDV2PLX"
google.com.  300  IN  TXT  "onetrust-domain-verification=0d477fe608074e6f9c12bca7826035cc"
google.com.  300  IN  TXT  "cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b"
google.com.  300  IN  TXT  "Z29vZ2xl"
google.com.  300  IN  TXT  "onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0"
google.com.  300  IN  TXT  "google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o"
google.com.  300  IN  TXT  "work-accounts-domain-verification=Tcj6JjIMZOw2KsSEw2Nt2rLae89tN6"
google.com.  21600  IN  NS  ns4.google.com.
google.com.  21600  IN  NS  ns1.google.com.
google.com.  21600  IN  NS  ns3.google.com.
google.com.  21600  IN  NS  ns2.google.com.
google.com.  29  IN  SOA  ns1.google.com. dns-admin.google.com. 953810495 900 900 1800 60
What does each field mean?

Field reference

TTL

Aantal seconden dat een downstream resolver het record mag cachen voordat hij de autoritatieve server opnieuw bevraagt. Korte TTL (60–300) verspreidt wijzigingen snel maar verhoogt het aantal hits; lange TTL (1u–1d) verlaagt belasting maar vertraagt DNS-aanpassingen.

A-record

Mapt een hostnaam naar een 32-bit IPv4-adres (bijv. <code>example.com → 93.184.216.34</code>). Het meest voorkomende DNS-recordtype; webverkeer begint met een A-lookup.

AAAA-record

IPv6-equivalent van A — een 128-bit adres (bijv. <code>2606:2800:220:1::93:184:216:34</code>). Moderne hosts publiceren zowel A als AAAA; de resolver kiest op basis van de connectiviteit van de client.

MX-record

Vermeldt de hostna(a)m(en) van mailexchangers plus een prioriteit — de laagste prioriteit wordt eerst geprobeerd. Zonder MX kan er geen e-mail aan het domein worden afgeleverd. Voorbeeld: <code>10 mail.example.com</code>.

CNAME

Canonical Name: vertelt de resolver "om mij te vinden, zoek in plaats daarvan X op". Kan niet samengaan met andere records op dezelfde naam en mag niet staan op de zone apex (het kale domein). Nuttig voor CDN's en SaaS-aanbieders.

TXT

Oorspronkelijk willekeurige tekst, vandaag drager van machine-readable beleid: SPF (toegestane mailafzenders), DKIM (signing keys), DMARC (e-mailauthenticatiebeleid) en eigendomsverificatie-tokens voor Google/Microsoft/AWS.

NS

Vermeldt de servers die de feitelijke zonedata bevatten. Het TLD-register geeft NS-records terug tijdens de referral chain; resolvers vragen vervolgens al het overige bij deze servers op. NS wijzigen is in feite een hernieuwde delegatie.

PTR

Mapt een IP terug naar een naam. Verplicht voor mailservers — veel providers weigeren SMTP vanaf IP's zonder of met een generieke PTR. De houder van het IP-blok (niet de domeineigenaar) beheert PTR-records.

SOA

Elke zone heeft exact één SOA: master-NS, contact-e-mail, serienummer (wordt verhoogd bij wijzigingen — secondaries detecteren updates ermee), refresh/retry/expire-timers, default negative-cache TTL.

CAA

Certification Authority Authorization beperkt welke CA's certificaten voor het domein mogen uitgeven. Voorbeeld: <code>0 issue "letsencrypt.org"</code> blokkeert elke CA behalve Let's Encrypt. CA's moeten CAA respecteren vóór uitgifte.

Resolver

De publieke recursieve resolver die we hebben bevraagd: Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9). Verschillende resolvers kunnen verschillende antwoorden geven door TTL-races, anycast of geo-targeted DNS.

Over deze 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.

Veelgestelde vragen

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.