PTR Record Checker

Enter an IP address to look up its PTR (Pointer) record — the reverse DNS entry that maps an IP back to a hostname. PTR records are critical for email deliverability because many mail servers reject email from IPs without valid reverse DNS.

Enter IP Address

What Is a PTR Record?

A PTR (Pointer) record is a type of DNS record that maps an IP address to a hostname — the reverse of what an A record does. While an A record answers "what IP does this domain point to?", a PTR record answers "what hostname does this IP belong to?" This reverse mapping is stored in a special DNS zone called in-addr.arpa.

For example, the PTR record for IP 203.0.113.10 is stored at 10.113.0.203.in-addr.arpa (note the reversed octets). You can look up any DNS record type with our DNS Lookup tool, and verify A records with our IP Address Lookup.

Why PTR Records Matter for Email

PTR records are one of the first things a receiving mail server checks when your server connects. Without a valid PTR record, many servers will immediately reject the connection. Here's why PTR records are so important:

Reason	Explanation	Impact Without PTR
Spam prevention	Legitimate servers have rDNS; spammers often don't	Rejected by 30-50% of servers
Server identity	Confirms the server is who it claims to be	SPF alignment issues
FCrDNS validation	Forward-confirmed rDNS proves IP/hostname match	Trust score reduced
Policy compliance	Required by RFC 5321 and most ISP policies	Non-compliant sending
Blacklist avoidance	Missing PTR is a common listing trigger	Higher blacklisting risk

Pro Tip: Your PTR record should match the hostname your mail server uses in the SMTP EHLO/HELO greeting, and that hostname's A record should resolve back to the same IP. This three-way match (IP → PTR → A → IP) is called Forward-Confirmed Reverse DNS (FCrDNS) and is the gold standard for mail server identity verification. Use our DNS Lookup to verify all three records match.

How PTR Records Work

The PTR lookup process involves a special DNS zone called in-addr.arpa:

Reverse the IP octets: 203.0.113.10 becomes 10.113.0.203
Append the arpa domain: 10.113.0.203.in-addr.arpa
Query DNS for PTR type: The response contains the hostname
Optionally verify forward DNS: Look up the returned hostname's A record to confirm it points back to the original IP

# Command line PTR lookup examples
# Windows
nslookup -type=PTR 10.113.0.203.in-addr.arpa

# Linux/macOS
dig -x 203.0.113.10
host 203.0.113.10

PTR Record vs Other DNS Records

Record Type	Direction	Maps	Used For
A Record	Forward	Domain → IPv4	Website hosting, service discovery
AAAA Record	Forward	Domain → IPv6	IPv6 service discovery
PTR Record	Reverse	IP → Domain	Email verification, server identity
MX Record	Forward	Domain → Mail server	Email routing
CNAME Record	Forward	Domain → Domain	Aliases and CDN setup

Understanding how these records work together is fundamental to DNS and network administration. If you're managing your own router and need to change DNS settings, make sure your DNS resolver can handle reverse lookups correctly.

Note: PTR records can only be created by the entity that controls the IP address block — typically your hosting provider, ISP, or cloud provider. Unlike forward DNS records that you manage through your domain registrar, reverse DNS requires coordination with whoever owns the IP range. Contact your provider's support team to request PTR record configuration.

How to Set Up a PTR Record

Setting up a PTR record depends on your hosting environment:

Hosting Type	How to Set PTR	Typical Turnaround
VPS (DigitalOcean, Vultr, Linode)	Usually set automatically from droplet hostname; change in control panel	Instant to 24 hours
AWS EC2	Request via AWS support or use Elastic IP rDNS settings	24-48 hours
Dedicated Server	Request through hosting provider's control panel or support ticket	24-48 hours
Residential ISP	Contact ISP support; many don't offer this for residential accounts	Varies widely
Google Cloud	Set via instance metadata or gcloud CLI	Instant to 24 hours

After setting up your PTR record, wait for DNS propagation (up to 48 hours) and then use this tool to verify it's working. Also check that your SMTP ports are open and your subnet is correctly configured.

Troubleshooting PTR Issues

Common PTR record problems and their solutions:

No PTR record exists — Contact your hosting provider to create one. This is the most common issue for new mail servers.
PTR doesn't match EHLO hostname — Update either the PTR record or your mail server's EHLO greeting to match. Check your mail server config.
FCrDNS fails — The PTR hostname's A record doesn't resolve back to the original IP. Fix the A record to point to your mail server IP.
Generic PTR hostname — Hostnames like host-203-0-113-10.provider.com look spammy. Request a custom PTR that matches your mail domain.
DNS propagation delay — Changes can take up to 48 hours. Check TTL values and try different DNS resolvers.

If you're experiencing DNS issues, try changing your DNS resolver to Google (8.8.8.8) or Cloudflare (1.1.1.1) to rule out resolver problems. You can use our Speed Test and Ping Test to verify basic connectivity.

PTR Records and Email Security

PTR records are part of a broader email security ecosystem. For maximum deliverability, combine PTR with these other mechanisms:

SPF — Publish an SPF TXT record listing authorized sending IPs. Verify with our SPF Record Checker.
DKIM — Sign outgoing email and publish the public key in DNS.
DMARC — Set a policy for handling authentication failures.
TLS — Enable STARTTLS or implicit TLS on your mail server. Verify with our SSL Certificate Checker.
Network security — Secure your network to prevent compromised devices from sending spam.

Key Takeaways

A PTR record maps an IP address back to a hostname — the reverse of an A record.
Many mail servers reject email from IPs without valid PTR records.
Forward-Confirmed Reverse DNS (FCrDNS) — where PTR and A records match — is the gold standard.
PTR records can only be set by the IP address owner (hosting provider or ISP), not through your domain registrar.
Your PTR hostname should match your mail server's EHLO/HELO greeting.
Combine PTR with SPF, DKIM, and DMARC for complete email authentication.

Video: Understanding Reverse DNS and PTR Records

Related Tools and Guides

Frequently Asked Questions

What is a PTR record in simple terms?

A PTR record is a DNS entry that maps an IP address to a hostname — the opposite of a regular A record which maps a hostname to an IP. It answers the question "what domain name belongs to this IP?" and is primarily used for email server verification and network troubleshooting.

Do I need a PTR record to send email?

While technically not required by the SMTP protocol itself, the vast majority of mail servers will reject or spam-filter emails from IPs without a valid PTR record. In practice, a PTR record is essential for reliable email delivery. RFC 5321 recommends that all SMTP servers have valid reverse DNS.

Who can create a PTR record?

Only the entity that controls the IP address block can create PTR records. This is typically your hosting provider, VPS provider, or ISP — not your domain registrar. Contact your provider's support team and request that they set up a PTR record for your IP pointing to your mail server hostname.

What should my PTR record be set to?

Your PTR record should match the hostname your mail server uses in its EHLO/HELO greeting, and that hostname should have an A record pointing back to the same IP. For example, if your mail server greets as mail.example.com, the PTR should resolve to mail.example.com, and mail.example.com should resolve to your IP.

What is Forward-Confirmed Reverse DNS (FCrDNS)?

FCrDNS means that the reverse DNS lookup (PTR) and forward DNS lookup (A record) agree with each other. If IP 203.0.113.10 has a PTR record pointing to mail.example.com, and mail.example.com's A record points back to 203.0.113.10, then FCrDNS is confirmed. This is the strongest form of IP-to-hostname verification.

How long does it take for PTR changes to propagate?

PTR record changes typically propagate within 24-48 hours, though some providers apply changes much faster. The propagation speed depends on the TTL of the existing record and the caching behavior of DNS resolvers. You can check propagation status by querying different DNS servers.

About Tommy N.

Tommy is the founder of RouterHax and a network engineer with 10+ years of experience in home and enterprise networking. He specializes in router configuration, WiFi optimization, and network security. When not writing guides, he's testing the latest mesh WiFi systems and helping readers troubleshoot their home networks.