DNS Checker
Free, no signup. Ask three public resolvers the same DNS question. When their answers differ, you can see the propagation evidence instead of guessing.
For PTR, enter either a reverse DNS name or an IPv4 address. Each resolver is queried independently.
Checks run from our server; we fetch the URL you enter and don't keep the results. Queries use Cloudflare, Google, and Quad9 DNS-over-HTTPS. Results are cached briefly (about one minute) so this is not an instant authoritative DNS check. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Sample report
Illustrative example — fixed resolver answers
- Cloudflare: A 192.0.2.10 (TTL 300s)
- Google: A 192.0.2.10 (TTL 240s)
- Quad9: A 192.0.2.20 (TTL 300s)
Signal to review: resolver answers differ. This can be propagation, split-horizon behavior, or a resolver issue; it is not automatically a bad zone.
How to use it
- Enter a domain or DNS name and select the record type.
- Choose Look up DNS to query Cloudflare, Google, and Quad9 independently.
- Compare answer values and TTLs, then review mismatch or resolver-error flags.
- Use the copyable zone-file reference for notes only; edit real records at the authoritative DNS provider.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Services suggested by returned records
These matches describe observed DNS dependencies only. They do not prove an account is active or identify the origin host.
Signals to review
Copy observed answers as a zone-file reference
Rate this tool
What the results mean
Matching values across three recursive resolvers are consistency evidence. Different TTLs alone are normal as caches age. A value mismatch means the resolver views differ. A DNS status or network failure belongs only to that resolver and is not converted into a clean answer.
How it works
The browser sends three parallel DNS-over-HTTPS requests through the bounded endpoint. The response preserves each resolver’s status, typed answers, TTLs, authority context, and errors. Deterministic comparison rules flag differing values or unavailable resolvers, explain the selected record and response status in plain language, identify a small curated set of provider-controlled hostnames only when they appear in returned records, and convert observed answers into zone-style text.
Features
- Eleven common record types including PTR and SRV.
- Side-by-side Cloudflare, Google, and Quad9 results.
- Plain-language record and DNS status explanations.
- Evidence-led delivery and email-service hints from returned hostnames.
- TTL, resolver status, and propagation flags.
- Copyable observed-answer reference.
Limitations
These are cached recursive views, not direct authoritative queries, and results are briefly cached by this service. Provider hints cover only a small curated hostname set and do not prove an account is active or reveal an origin. The tool does not trace delegation, edit records, validate DNSSEC chains, test every geographic resolver, or prove the cause of a mismatch.
Frequently asked questions
Why do the three resolvers disagree?
Different recursive resolvers can retain old answers until their TTL expires. A mismatch can indicate propagation, split-horizon DNS, or a resolver failure; it is not by itself proof of a misconfiguration.
Does the zone-file export change DNS?
No. It is a copyable representation of observed answers, not an authoritative export and never a write to your DNS provider.
Which DNS record types can I check?
The checker supports A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV, and PTR. PTR accepts an IPv4 address or a reverse-DNS name.
Are these authoritative DNS answers?
No. Cloudflare, Google, and Quad9 are recursive resolvers. Their cached view is useful for propagation checks, but the domain’s authoritative nameservers are the source of record truth.
Feature requests for Dns Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Über das Tool
Frage drei öffentliche rekursive Resolver dieselbe DNS-Frage und vergleiche ihre Antworten und TTLs. Unterschiede werden als Propagations-, Split-Horizon- oder Resolver-Hinweis sichtbar, ohne vorschnell eine Fehlkonfiguration zu behaupten.
Die Ergebnisse sind eine kopierbare Darstellung beobachteter Antworten, kein autoritativer Zonendatei-Export und niemals eine Änderung beim DNS-Anbieter.
Funktionen
- Seitlicher Vergleich von Cloudflare, Google und Quad9 für A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV und PTR
- PTR-Abfragen per Reverse-DNS-Name oder IPv4-Adresse
- TTL-, Mismatch- und Resolver-Fehler-Hinweise
- Kopierbare Zonendatei-Referenz für Notizen, ohne echte DNS-Einträge zu bearbeiten
Funktionsweise
Gib eine Domain oder einen DNS-Namen sowie den Record-Typ ein. Jeder Resolver wird unabhängig abgefragt; Antwortwerte und TTLs werden gegenübergestellt. Mismatch- und Resolverfehler werden als überprüfbare Signale markiert.
Einschränkungen
- Rekursive Resolver können alte Antworten bis zum Ablauf der TTL behalten; Unterschiede beweisen allein keine Fehlkonfiguration.
- Die vorgeschlagenen Dienste beschreiben nur beobachtete DNS-Abhängigkeiten und beweisen weder ein aktives Konto noch den Origin-Host.
- Autoritative Nameserver des Domains sind die Quelle der Wahrheit; die kopierbare Ausgabe schreibt niemals zum DNS-Provider.
Häufig gestellte Fragen
Welche DNS-Record-Typen kann ich prüfen?
Der Prüfer unterstützt A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV und PTR. PTR akzeptiert eine IPv4-Adresse oder einen Reverse-DNS-Namen.
Warum unterscheiden sich die drei Resolver?
Unterschiedliche rekursive Resolver können alte Antworten bis zum TTL-Ablauf cachen. Ein Unterschied kann Propagation, Split-Horizon-DNS oder einen Resolverfehler bedeuten, ist aber allein kein Beweis für eine falsche Zone.
Sind das autoritative DNS-Antworten?
Nein. Cloudflare, Google und Quad9 sind rekursive Resolver. Ihre gecachte Sicht ist für Propagationsprüfungen nützlich; die autoritativen Nameserver bleiben maßgeblich.
Ändert der Zonendatei-Export DNS?
Nein. Er ist eine kopierbare Referenz beobachteter Antworten und schreibt nie zum DNS-Provider. Bearbeite echte Records beim autoritativen Anbieter.