Skip to main content

Reverse DNS Lookup (PTR)

Find the hostname associated with any IP address

Need to know the domain name associated with an IP? Enter an IPv4 or IPv6 address and instantly get its PTR records, each with an automatic forward-confirmed reverse DNS (FCrDNS) check and a clear verdict.

Advanced options

Key features

IPv4 and IPv6

Works with both formats. Automatically queries in-addr.arpa or ip6.arpa based on the address.

Consistency check

The tool automatically confirms that the PTR matches the A/AAAA record (forward-confirmed reverse DNS).

Email deliverability

A correct PTR improves your mail server reputation. Essential to avoid spam filters.

Network diagnostics

Quickly identify machines in your logs with readable names instead of number sequences.

100% free

No registration required. Perform as many reverse lookups as needed without limits.

What is Reverse DNS?

Reverse DNS allows you to find the hostname associated with an IP address. It's the inverse operation of standard DNS resolution.

Common use cases:

  • Email deliverability: Verify your mail server has a correct PTR
  • Network diagnostics: Identify machines in logs with readable names
  • Security: Verify the identity of incoming connections
  • Auditing: Validate consistency between forward and reverse zones

How does reverse DNS work?

For IPv4 (in-addr.arpa)

The address is reversed octet by octet, then .in-addr.arpa is added:

IP: 203.0.113.10
Query: 10.113.0.203.in-addr.arpa → PTR → mail.captaindns.com

For IPv6 (ip6.arpa)

Each hexadecimal nibble is separated and reversed:

IP: 2001:db8::1
Query: 1.0.0.0...8.b.d.0.1.0.0.2.ip6.arpa → PTR → server.captaindns.com

The importance of forward/reverse consistency

For credibility, DNS configuration must be consistent:

DirectionQueryResult
Forwardmail.captaindns.com → A →203.0.113.10
Reverse203.0.113.10 → PTR →mail.captaindns.com

If both match, consistency is validated. This is what mail servers and many security services verify, and the tool confirms it automatically (forward-confirmed reverse DNS).

An IP address can also return more than one PTR record. The tool lists every PTR it finds and shows a forward-confirmed verdict for each record individually.


Reverse DNS and email deliverability

Why it's essential

Mail servers perform several checks:

  1. PTR exists: The IP must have a PTR record
  2. PTR is consistent: The PTR name must resolve back to the original IP
  3. Professional name: Avoid generic names like "static-203-0-113-10.isp.net"

Example of correct configuration

Server IP: 203.0.113.25
PTR: 203.0.113.25 → smtp.yourdomain.com
A: smtp.yourdomain.com → 203.0.113.25

FAQ - Frequently asked questions

Q: What is a PTR record?

A: A PTR (Pointer) record is the reverse of an A/AAAA record. Instead of resolving a name to an IP address, it resolves an IP address to a hostname. This is the reverse DNS mechanism.


Q: Why is reverse DNS important for emails?

A: Mail servers often verify that the sending IP has a valid and consistent PTR. Without a PTR or with an inconsistent one, your emails may be marked as spam or rejected.


Q: What is forward/reverse consistency?

A: Consistency means the name returned by the PTR must itself resolve back to the original IP via an A or AAAA record. This cross-check is required by many spam filters.


Q: How do I configure reverse DNS for my server?

A: Reverse DNS is typically configured by your hosting provider or IP provider. Contact them to request a PTR record pointing to your hostname.


Q: Why doesn't my IP have a PTR?

A: Only the IP block owner (your host or ISP) can configure PTR records. Residential IPs often don't have custom PTR records. Contact your provider to request one.


Q: What's the difference between in-addr.arpa and ip6.arpa?

A: in-addr.arpa is the zone for IPv4 reverse DNS (reversed octets). ip6.arpa is for IPv6 (reversed hex nibbles). Both work on the same principle.


Complementary tools

ToolPurpose
Whois IPIdentify the owner of an IP
My IP AddressDisplay your public IP
IP Blacklist CheckCheck your sending IP reputation on DNSBLs for deliverability

Useful resources