PTR Record Propagation CheckerVerify reverse DNS is live across independent global resolvers
- 7 independent networks
- Records + DNS flags
- No ads, no sign-up
Independent networks
7 public DNS networks, queried in parallel
Every test query is answered by these unaffiliated resolvers on separate networks and infrastructure. When they agree, you can trust the result.
- 8.8.8.8
Google Public DNS
Google LLC · North America
- 1.1.1.1
Cloudflare
Cloudflare, Inc. · Global Anycast
- 94.140.14.14
AdGuard DNS
AdGuard Software Ltd. · Europe
- 45.90.28.0
NextDNS
NextDNS, Inc. · Global Anycast
- 185.222.222.222
DNS.SB
xTom / Layer0 · Europe
- 223.5.5.5
Alibaba DNS
Alibaba Cloud · Asia
- 119.29.29.29
DNSPod
Tencent Cloud · Asia
How it works
A test query for flag propagation check, done right
Most checkers query a single resolver or a set of geographically labelled servers behind the same anycast network. isPropagated queries genuinely independent DNS operators and compares both their records and their response flags.
Enter a domain and run the test query
Type any domain, pick a record type (A, AAAA, CNAME, MX, TXT, NS and more), then run a single test query that fans out to every network at once.
We query independent global networks
Instead of asking one resolver, we ask several unaffiliated public DNS networks in parallel — across North America, Europe and Asia — so no single cache can mislead you.
Compare records and DNS flags
Each network returns its answer plus the DNS response flags (AD, CD, RA, RD, TC). We check that both the records and the flags agree before calling a domain propagated.
Read the propagation verdict
A clear consensus score shows how many networks resolved the record and whether their answers match — so you know the moment a change is live everywhere.
What is a PTR record and why does reverse DNS propagation matter?
A PTR (Pointer) record provides reverse DNS lookup — it maps an IP address back to a hostname. For example, the IP 198.51.100.1 might have a PTR record pointing to mail.example.com. PTR records live in special in-addr.arpa (IPv4) or ip6.arpa (IPv6) zones that are controlled by the IP address owner, usually the hosting provider or ISP rather than the domain owner.
PTR records matter most for email deliverability. Many mail servers and spam filters check that the sending IP's PTR record matches a hostname that forward-resolves back to the same IP (a "forward-confirmed reverse DNS" or FCrDNS check). A mail server without a valid PTR record is likely to be rejected or marked as spam by major receivers like Gmail and Microsoft.
To set a PTR record, you typically configure it through your server's hosting provider or ISP panel, not through your domain registrar's DNS. Changes to PTR records are controlled by the owner of the IP address block.
Checking PTR record propagation
To check a PTR record, enter the reverse DNS name in the input field. For an IPv4 address, reverse the octets and append .in-addr.arpa — for example, IP 203.0.113.5 becomes 5.113.0.203.in-addr.arpa. Select PTR from the dropdown and run the test.
When all resolvers return the correct hostname for your IP, reverse DNS is live everywhere. If some return NXDOMAIN, the PTR record has not propagated from the IP owner's authoritative servers yet — contact your hosting provider to confirm the record was set correctly.
FAQ
Common questions about ptr record propagation checker
How do I set a PTR record for my mail server IP?
PTR records are controlled by the owner of the IP address block, not by the domain owner. Log in to your server or VPS hosting panel (AWS EC2 Elastic IPs, DigitalOcean Droplets, Hetzner, etc.) and set the reverse DNS for the IP address there. The change may take minutes to a few hours to propagate.
How long does PTR record propagation take?
PTR records typically propagate within 1–4 hours, depending on the TTL set by your hosting provider. The in-addr.arpa zone is served by the IP block owner's nameservers, so propagation speed depends on their infrastructure.
Why is PTR record verification important for email?
Many receiving mail servers perform a reverse DNS check on the connecting IP. If the IP has no PTR record, or the PTR does not match the hostname used in the SMTP EHLO greeting, the message is likely to be rejected or marked as spam. Setting a matching PTR record is one of the fundamental steps to good email deliverability.
What is a forward-confirmed reverse DNS (FCrDNS) check?
FCrDNS (also called forward-confirmed PTR) means: (1) the IP has a PTR record pointing to a hostname, and (2) that hostname has an A record pointing back to the same IP. Both checks must pass. Use this tool to verify the PTR side, then separately verify that your mail server hostname resolves to the same IP.