🌐 DNS Propagation Checker avatar

🌐 DNS Propagation Checker

Pricing

Pay per event

Go to Apify Store
🌐 DNS Propagation Checker

🌐 DNS Propagation Checker

Check DNS propagation across 8 global resolvers (Google, Cloudflare, Quad9, OpenDNS). Supports A, AAAA, MX, TXT, CNAME, NS, SOA records. Detect inconsistencies after DNS changes.

Pricing

Pay per event

Rating

0.0

(0)

Developer

太郎 山田

太郎 山田

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Check DNS propagation across 8 global resolvers (Google, Cloudflare, Quad9, OpenDNS). Detect inconsistencies after DNS changes.

Store Quickstart

Start with the Quickstart template (3 domains, A records). For multi-record audits, use Full DNS Audit (A, AAAA, MX, TXT, CNAME, NS).

Key Features

  • 🌐 8 global DNS resolvers — Google, Cloudflare, Quad9, OpenDNS, Cisco Umbrella, Level3, Verisign, Dyn
  • 📋 7 record types — A, AAAA, MX, TXT, CNAME, NS, SOA
  • ⚠️ Inconsistency detection — Instantly spots resolvers that disagree
  • ⏱️ TTL reporting — See caching behavior across resolvers
  • 📦 Bulk domains — Check up to 200 domains per run
  • 🔑 No API key needed — Uses Node.js built-in dns.Resolver

Use Cases

WhoWhy
DNS administratorsVerify DNS changes propagated globally before changing URLs
Hosting migrationsConfirm nameserver switch completed at all resolvers
Email deliverabilityCheck MX, SPF, DKIM TXT records consistency
Security teamsDetect DNS hijacking via inconsistent resolver responses
DevOps teamsPre-deploy DNS verification for production cutover

Input

FieldTypeDefaultDescription
domainsstring[](required)Domains to check (max 200)
recordTypesstring[]["A"]A, AAAA, MX, TXT, CNAME, NS, SOA

Input Example

{
"domains": ["example.com", "api.example.com"],
"recordTypes": ["A", "MX", "TXT"]
}

Output Example

{
"domain": "example.com",
"recordType": "A",
"resolvers": [
{"name": "Google", "ip": "8.8.8.8", "values": ["93.184.216.34"], "ttl": 86400},
{"name": "Cloudflare", "ip": "1.1.1.1", "values": ["93.184.216.34"], "ttl": 86400}
],
"isConsistent": true,
"inconsistencies": []
}

FAQ

Why use 8 resolvers?

DNS caching varies by resolver. Checking multiple reveals which have updated after a change.

What's a typical propagation time?

TTL-dependent. Most DNS changes propagate globally within 1-24 hours.

Does it check geographic propagation?

No — all resolvers queried are major public ones. For geographic checks, use specialized tools.

Can I check private DNS?

No, only public DNS. Internal/private domains return NXDOMAIN.

DevOps & Tech Intel cluster — explore related Apify tools:

Cost

Pay Per Event:

  • actor-start: $0.01 (flat fee per run)
  • dataset-item: $0.005 per output item

Example: 1,000 items = $0.01 + (1,000 × $0.005) = $5.01

No subscription required — you only pay for what you use.