Arsal • Location • Starter
Why teams use this PTR checker
Gmail, Outlook, Yahoo and most filters require valid PTRs to accept mail. Confirm rDNS before launching email campaigns.
We resolve the PTR hostname forward and confirm it points back to the original IP, so you do not have to chain commands.
See the actual in-addr.arpa or ip6.arpa zone, plus the authoritative nameservers and SOA controlling reverse DNS.
Enter a domain and we resolve A and AAAA records first, then run reverse DNS on every IP automatically.
The PTR hostname often reveals the hosting provider, datacenter, or ISP behind an IP, useful for audits and incident response.
Clean output with status pills, perfect for sharing with hosting vendors when you ask them to set or fix rDNS.
How it works
If you enter a domain we resolve A and AAAA records first. If you enter an IP we use it directly.
We build the correct in-addr.arpa (IPv4) or ip6.arpa (IPv6) zone and fetch every PTR record returned.
The PTR hostname is forward-resolved back to its IP. If it matches, the PTR is FCrDNS-valid and trusted by mail receivers.
Note: rDNS is set by the owner of the IP block (your hosting provider or ISP), not your DNS provider. To change a PTR, open a ticket with whoever issued the IP.
The best out there
A PTR record is a DNS pointer record that maps an IP address to a hostname. It powers reverse DNS lookups and is required by major mail receivers like Gmail and Outlook for email deliverability.
FCrDNS (Forward-confirmed reverse DNS) means the PTR hostname forward-resolves back to the original IP. Many anti-spam systems require FCrDNS to accept mail.
For IPv4, the octets are reversed and queried under in-addr.arpa (for example 4.4.8.8.in-addr.arpa for 8.8.4.4). For IPv6, hex nibbles are reversed under ip6.arpa. The PTR record returned is the hostname assigned to that IP.
PTR records are managed by whoever owns the IP block, usually the hosting provider or ISP. Contact them and ask them to set rDNS for your IP. Without it, your outgoing mail will likely be rejected.
Technically yes, but it is best practice to keep one PTR per IP. Multiple PTRs can confuse mail receivers and complicate FCrDNS validation.