Check PTR records, verify reverse DNS configuration, and validate email server hostname mapping
Reverse DNS (rDNS) is the process of resolving an IP address back to a domain name, which is the opposite of regular DNS lookup. This is accomplished through PTR (Pointer) records. Reverse DNS is crucial for email delivery, network troubleshooting, and server verification.
Reverse DNS performs the inverse function of forward DNS:
This reverse mapping is stored in special DNS zones (in-addr.arpa for IPv4, ip6.arpa for IPv6) and managed by whoever controls the IP address block, typically your ISP or hosting provider.
A PTR (Pointer) record is a type of DNS record that provides the reverse mapping from an IP address to a hostname. Key characteristics:
Reverse DNS is critically important for several reasons:
For email servers, proper reverse DNS is essential:
The gold standard for reverse DNS is "Forward-Confirmed Reverse DNS" (FCrDNS):
Example of valid FCrDNS:
192.0.2.1 → mail.example.com → 192.0.2.1 ✓
Example of invalid FCrDNS:
192.0.2.1 → mail.example.com → 192.0.2.99 ✗
Setting up reverse DNS requires coordination with your IP address provider:
No PTR Record: Contact your ISP/hosting provider to create one. You cannot set this yourself unless you own the IP block.
PTR Doesn't Match Forward DNS: Update either the PTR or A/AAAA record to match. Both should resolve to each other.
Generic Hostname: Request a custom PTR from your provider pointing to your actual mail server hostname.
Multiple IPs, One Hostname: This is acceptable. One hostname can have multiple IPs in forward DNS.
Shared Hosting: Many shared hosting IPs have generic PTR records. Consider dedicated IP for email sending.
IPv6 reverse DNS works similarly but uses ip6.arpa zones instead of in-addr.arpa. Due to the length of IPv6 addresses, reverse zones are more complex:
Missing or misconfigured reverse DNS can severely impact email deliverability:
Check reverse DNS and PTR records for any IP address instantly
Automatically verify forward-confirmed reverse DNS (FCrDNS)
Essential for validating mail server configuration and deliverability
Reverse DNS (rDNS) is a DNS lookup that returns a domain name from an IP address - the opposite of regular DNS which returns an IP from a domain name. It uses PTR (pointer) records to map IPs to hostnames. For example: IP 8.8.8.8 reverse looks up to dns.google. This is essential for email servers, network troubleshooting, and server verification.
A PTR (Pointer) record is a type of DNS record that provides the reverse mapping from an IP address to a hostname. It's stored in special reverse DNS zones (in-addr.arpa for IPv4, ip6.arpa for IPv6). PTR records are essential for email servers - many mail servers require valid PTR records to accept incoming mail. They help verify legitimate servers versus spam sources and improve sender reputation.
Enter an IP address in the checker above and click "Check PTR". We'll perform a reverse DNS lookup and show: (1) The PTR record (hostname) if it exists, (2) Forward DNS verification - checking if the hostname resolves back to the same IP, (3) Validation status - whether it's properly configured, (4) Any warnings or issues. You can also click "Use My IP Address" to check your current IP automatically.
Many email servers require valid reverse DNS (PTR records) to accept incoming mail. Without proper reverse DNS: (1) Your emails may be rejected entirely, (2) Messages may be marked as spam, (3) Deliverability drops significantly, (4) Major providers like Gmail and Outlook check PTR, (5) Sender reputation suffers. Proper reverse DNS proves your mail server is legitimate and not a spam source. It's considered best practice for all mail servers.
You cannot set up reverse DNS yourself - you must contact whoever controls your IP address block (typically your ISP or hosting provider): (1) Contact your ISP/hosting provider, (2) Request PTR record creation, (3) Provide the IP and desired hostname, (4) Ensure forward DNS (A record) also exists, (5) Wait 24-48 hours for propagation, (6) Verify with our checker. Most providers offer this service, sometimes called "rDNS setup" or "PTR record configuration".
Forward-Confirmed Reverse DNS (FCrDNS) means the reverse DNS matches forward DNS in both directions: (1) Reverse lookup: IP → hostname (PTR), (2) Forward lookup: hostname → IP (A record), (3) The IP matches in both directions. Example: 192.0.2.1 → mail.example.com → 192.0.2.1 ✓. This is the gold standard and what email providers look for. Our checker automatically verifies FCrDNS and shows if your setup passes.
If PTR and forward DNS don't match, it fails FCrDNS validation: (1) IP reverse looks up to hostname1, but (2) hostname1 forward looks up to different IP. This causes email delivery issues. Solutions: Update the PTR record to match your A record, or update your A record to match the PTR. Both should point to each other. Contact your hosting provider to fix PTR, update A records in your DNS settings. Test again after changes propagate.
No, each IP address should have only ONE PTR record. However, one hostname can have multiple A records (multiple IPs). This is asymmetric: IP → hostname (one PTR), hostname → IPs (multiple A records possible). For mail servers, the PTR should point to your primary mail hostname. If you have multiple mail servers, each should have its own IP with its own PTR pointing to its specific hostname.
ISPs often set default PTR records with generic patterns like "host-123-45-67-89.isp.com" or "123-45-67-89.static.provider.net". This is problematic for mail servers. Solutions: (1) Request a custom PTR from your ISP pointing to your mail server hostname (e.g., mail.yourdomain.com), (2) Some ISPs offer this free, others charge, (3) Or get a dedicated IP from hosting provider with custom PTR included. Generic hostnames hurt email deliverability.
While reverse DNS is most critical for mail servers, it's still useful for: (1) Network troubleshooting and identification, (2) Security logging (shows hostnames instead of IPs), (3) Server verification and legitimacy, (4) Professional appearance. However, if you're only hosting websites (not sending email from the server), it's less critical. Focus on reverse DNS if you: run mail servers, send email from servers, require professional network setup, need detailed logging.