Skip to main content
MULTI-RESOLVER DNS CONSENSUS & PROPAGATION PROBE
🌐

DNS Propagation Checker

Evaluate DNS record consistency and cache agreement in real-time across independent DNS-over-HTTPS (DoH) recursive resolver networks.

✓Direct client-side DoH resolution (Google, Cloudflare, Quad9, OpenDNS, AdGuard, AliDNS, Control D, DNS.SB)
✓Resolver agreement percentage & record consensus matrix
ℹQueries independent Anycast DoH resolvers to verify cross-network DNS consistency
Resolver Consensus0% Agreement
Target Host
shrtx.in
Record Type
A
Avg Latency
0 ms
Consensus Values
No records resolved

Multi-Resolver Consensus Matrix

Test Domains:
🌐
Google Public DNS
Global Anycast (8.8.8.8)
0 mspending
Querying node...
🌐
Cloudflare DNS (1.1.1.1)
Global Anycast (1.1.1.1)
0 mspending
Querying node...
🌐
Quad9 DNS (9.9.9.9)
Global Anycast (Privacy / Threat-blocking)
0 mspending
Querying node...
🌐
OpenDNS / Cisco Umbrella
Global Anycast (208.67.222.222)
0 mspending
Querying node...
🌐
AdGuard DNS
Global Anycast (Ad & Tracker Blocking)
0 mspending
Querying node...
🌐
Alibaba Cloud DNS
Global / APAC Anycast (223.5.5.5)
0 mspending
Querying node...
🌐
Control D
Global Anycast (76.76.2.0)
0 mspending
Querying node...
🌐
DNS.SB
Global Anycast (Privacy-focused)
0 mspending
Querying node...

Multi-Resolver DNS Consensus and Propagation Auditing

The DNS Propagation Checker queries independent public DNS-over-HTTPS (DoH) recursive resolver networks to evaluate record agreement, consistency, and cache consensus across major infrastructure providers. By submitting simultaneous encrypted queries to global networks like Google Public DNS, Cloudflare, Quad9, OpenDNS, and AdGuard, the tool measures how uniformly a domain's DNS changes have propagated.

Public DoH resolvers operate vast global Anycast routing topologies. When a query is initiated from your web browser, network routing automatically directs the request to the nearest geographic Point of Presence (PoP) operated by each provider. This utility audits resolver consensus and evaluates whether major Anycast providers have updated their cached Resource Records following domain configuration edits.

The visual interface inspects multiple record types including A (IPv4), AAAA (IPv6), CNAME (canonical alias), MX (mail exchange), TXT (domain verification), NS (nameservers), SOA (start of authority), and CAA (certificate authority authorization). A live consensus gauge displays the percentage of resolvers returning matching answer sets, allowing systems administrators to confirm migration readiness with confidence.

Core Tool Capabilities

  • Multi-Resolver Consensus Auditing: Queries Google, Cloudflare, Quad9, OpenDNS, and AdGuard simultaneously to compare returned Resource Records across distinct infrastructure networks.
  • Comprehensive Record Type Inspection: Supports querying standard record types including A, AAAA, CNAME, MX, TXT, NS, SOA, and CAA records.
  • Consensus Percentage Rating: Calculates an automated consensus score from 0% to 100% measuring agreement among independent resolver networks.
  • Encrypted DNS-over-HTTPS Transport: Transmits queries via RFC 8484 DNS-over-HTTPS to prevent ISP query manipulation and ensure transport integrity.
  • TTL and Cache Duration Reporting: Displays returned Time-to-Live (TTL) values from each resolver to help forecast remaining cache expiration windows.
  • Zero Backend Proxy Privacy: Dispatches DNS queries directly from client browser fetch interfaces to official public DoH endpoints without third-party proxy logging.

Local Browser Privacy

Your files are processed locally on your device. Files are not uploaded, transmitted, or stored on remote servers.

Once the page has loaded, you can disconnect your network connection and continue using this tool offline.

Target Use Cases

  • • Web Hosting and Server Migrations
  • • Email Authentication and SPF/DKIM Deployment
  • • SSL/TLS Certificate Issuance Troubleshooting
  • • Domain Name Server Re-delegation

Technical Specifications & Platform Limits

Supported Resolvers
Google, Cloudflare, Quad9, OpenDNS, AdGuard

Queries independent global recursive resolvers via DNS-over-HTTPS.

Record Types
A, AAAA, CNAME, MX, TXT, NS, SOA, CAA

Comprehensive coverage of routing, mail, and security record types.

Protocol Standard
RFC 8484 (DoH)

Standardized DNS queries transmitted over encrypted HTTPS connections.

Consensus Metric
0% to 100% agreement index

Calculates the ratio of resolvers returning identical answer sets.

Execution Boundary
Direct browser-to-resolver DoH

Dispatches queries directly from browser without intermediary server hops.

Step-by-Step Workflow

1

Enter Domain Name

Type your target fully qualified domain name into the search input. You can enter root domains or specific subdomains.

2

Select DNS Record Type

Choose the specific record type you wish to audit, such as A, AAAA, MX, or TXT. The query parameters adjust automatically.

3

Execute Consensus Query

Click the check propagation button to dispatch concurrent DNS-over-HTTPS requests to all resolver networks. Response times and status codes appear in real time.

4

Evaluate Consistency Results

Review the returned IP addresses, TTL values, and the calculated consensus score to verify update status. Confirm all providers show matching data.

Practical Real-World Use Cases

Web Hosting and Server Migrations

DevOps engineers and sysadmins verifying that new server IP addresses have been adopted by major public resolvers before decommissioning legacy hosts.

Email Authentication and SPF/DKIM Deployment

Email administrators checking TXT record propagation for SPF, DMARC, and DKIM public keys to ensure outbound email deliverability.

SSL/TLS Certificate Issuance Troubleshooting

Security administrators auditing CAA records across resolvers to confirm that Certificate Authorities can validate domain control.

Domain Name Server Re-delegation

Domain brokers and website managers monitoring NS record transitions during registrar transfers and DNS provider switches.

Frequently Asked Questions

How does this tool check DNS propagation from the browser?
The tool uses the DNS-over-HTTPS (DoH) protocol to send secure, encrypted DNS queries directly from your browser to the public APIs of independent resolver networks like Google Public DNS, Cloudflare, Quad9, OpenDNS, and AdGuard. It compares the returned answers to evaluate whether all providers hold identical record data.
Why do different resolvers show different DNS records during a migration?
DNS records are cached by recursive resolvers based on their Time-to-Live (TTL) value. When you update a record at your authoritative nameserver, resolvers retain their cached copy until the previous TTL expires. Resolvers with fresher cache queries or lower initial TTLs reflect changes sooner than those holding unexpired cache entries.
What is Anycast routing and how does it affect DNS queries?
Anycast routing allows multiple physical data centers around the world to share the same IP address. When your browser queries a public resolver like Google (8.8.8.8) or Cloudflare (1.1.1.1), internet routing protocols automatically direct your packet to the nearest geographic Point of Presence (PoP). Therefore, results reflect the cache state of the resolver node closest to your current network connection.
Why is my DNS change not showing even though the TTL has expired?
Some Internet Service Providers (ISPs) and corporate recursive resolvers enforce minimum cache ceilings, deliberately ignoring short TTLs (such as 60 or 300 seconds) and caching records for several hours. Additionally, negative caching (caching the non-existence of a domain via SOA records) can delay updates if queries were made before the record was created.
Are my domain lookups tracked or logged on a private server?
No. The queries are sent directly from your browser to the official public DNS-over-HTTPS endpoints of the selected providers. SHRTX does not route your queries through an intermediary server, and no search terms or domain names are recorded in any platform database.

Share this tool

Help others discover this utility. No login or registration required.