A PTR record lookup helps you find the hostname associated with an IP address using reverse DNS. It is useful for checking email server configurations, investigating hosting connections, and troubleshooting DNS records.
Enter a public IPv4 or IPv6 address in the PTR Record Lookup tool to check whether a reverse DNS hostname is configured.
Reverse DNS Checker
Enter a public IPv4 or IPv6 address to find its PTR hostname. Results come from a live DNS query.
Reverse DNS response
- IP address
- Reverse query name
- PTR hostname(s)
Queries are performed by this website's server using Cloudflare's public DNS-over-HTTPS resolver. The IP you enter is sent to this website and its reverse DNS query is sent to Cloudflare. Private and reserved IP addresses are not supported. This does not measure your internet speed or prove IP ownership.
What Is a PTR Record?
A PTR (Pointer) record is a type of DNS record that maps an IP address to a hostname.
Most people are familiar with standard DNS lookups, where a domain name is translated into an IP address. PTR records work in the opposite direction.
For example:
| Lookup type | Example |
|---|---|
| Forward DNS | dns.google → 8.8.8.8 |
| Reverse DNS | 8.8.8.8 → dns.google |
These examples illustrate the difference between forward and reverse lookups.
PTR records are commonly used by mail servers, hosting providers, network administrators, and troubleshooting tools.
A PTR record does not prove who owns an IP address, and its hostname should not be treated as verified identity information.
How to Check a PTR Record
Checking reverse DNS requires only an IP address.
- Enter an IP address. Type the IPv4 or IPv6 address you want to investigate.
- Start the lookup. Select the PTR lookup option to request reverse DNS information.
- Review the hostname. If a PTR record is returned, examine the associated hostname.
- Check the result status. A missing record, DNS error, or timeout requires a different interpretation.
- Verify forward DNS if needed. Check whether the returned hostname resolves back to the original IP address.
For example, you might check your dedicated hosting server’s public IP address to see whether the reverse DNS name matches the hostname configured for your mail server.
How Does Reverse DNS Lookup Work?
The Domain Name System supports special reverse lookup namespaces for IPv4 and IPv6 addresses.
When you request a PTR lookup, the DNS resolver queries the corresponding reverse DNS name instead of performing a normal domain-to-address lookup.
Reverse DNS for IPv4 Addresses
IPv4 reverse DNS uses the in-addr.arpa namespace.
For an IP address such as 192.0.2.25, the corresponding reverse lookup name is:
25.2.0.192.in-addr.arpa
The four address components are reversed before the lookup.
The resolver then requests a PTR record for that name. If a PTR record exists and is accessible, it may return a hostname.
Reverse DNS for IPv6 Addresses
IPv6 reverse lookups use the ip6.arpa namespace.
The address is expanded into its hexadecimal digits, and the digits are reversed and separated by dots to form the reverse lookup name.
You do not need to construct this name manually when using a lookup tool that supports IPv6.
Understanding PTR Lookup Results
A reverse DNS lookup may produce several different outcomes.
| Result | What it means |
|---|---|
| PTR record found | DNS returned one or more hostnames for the queried address. |
| No PTR record | The queried reverse DNS name has no PTR answer. |
| NXDOMAIN | The queried DNS name does not exist according to the DNS response. |
| Timeout | The resolver did not receive a usable response within the allowed time. |
| SERVFAIL | The DNS resolver or another server encountered a processing failure. |
| Invalid IP address | The submitted value is not a valid IP address. |
A successful PTR response does not necessarily mean the hostname points back to the same IP address.
To investigate that relationship, perform a separate forward DNS lookup using the returned hostname.
Why Are PTR Records Important?
1. Email Server Configuration
PTR records are especially relevant to servers that send email.
Receiving mail systems may consider reverse DNS information when evaluating connections from sending servers.
A missing or inconsistent reverse DNS configuration can contribute to email delivery problems, although PTR records alone do not determine whether messages reach recipients.
For a mail server, administrators should generally verify that the sending IP has an appropriate PTR hostname and that the hostname resolves back to the sending IP.
Other email authentication mechanisms, including SPF, DKIM, and DMARC, serve different purposes and should be configured separately where applicable.
2. Server and Hosting Troubleshooting
A PTR record can provide clues about the hostname assigned to a hosting server, VPS, or network address.
This information can help administrators compare DNS configuration with hosting records and investigate unexpected server behavior.
However, a hostname returned by reverse DNS is not reliable proof that a particular company operates the server.
3. Network Diagnostics
Reverse DNS names may appear in diagnostic tools, server logs, and network troubleshooting reports.
They can make some IP addresses easier to recognize.
A missing PTR record does not automatically indicate a connection failure. Many systems operate normally without publicly configured reverse DNS hostnames.
PTR Record vs. A Record vs. AAAA Record
These DNS record types perform related but different functions.
| Record | Purpose | Example |
|---|---|---|
| A | Maps a hostname to an IPv4 address | dns.google → 8.8.8.8 |
| AAAA | Maps a hostname to an IPv6 address | Hostname → IPv6 address |
| PTR | Maps an IP address to a hostname | 8.8.8.8 → dns.google |
A and AAAA records are used for forward DNS resolution. PTR records are used for reverse DNS resolution.
A domain can have multiple A or AAAA records, and reverse DNS information does not need to follow a one-to-one relationship in every configuration.
How to Fix a Missing or Incorrect PTR Record
If the lookup does not return the expected hostname, first determine who controls reverse DNS for the IP address.
Check the Correct IP Address
Make sure you are testing the public address assigned to the relevant service.
For an email server, use the actual outbound sending IP rather than assuming it is identical to the website’s hosting IP.
Contact the IP Address Provider
Reverse DNS is generally controlled through the organization responsible for the relevant IP address space or its delegated DNS administrator.
Depending on your hosting arrangement, PTR records may be managed through a hosting control panel, cloud provider, ISP, or dedicated server provider.
Adding an A record to your normal domain DNS settings does not automatically create a PTR record.
Verify Forward and Reverse DNS
For a typical single-host mail server configuration, check the following:
- The sending IP address has a PTR record pointing to the intended hostname.
- The hostname has a corresponding A or AAAA record.
- The forward lookup includes the original sending IP.
- The mail server’s hostname and provider settings are consistent with the intended configuration.
Some receiving systems use forward-confirmed reverse DNS checks, but their acceptance policies vary.
Allow for DNS Caching
After a DNS change, cached responses may remain visible until the relevant cache entries expire.
If you have recently changed a PTR record, repeat the lookup after the applicable caching period. Different resolvers may temporarily return different information.
Frequently Asked Questions
What does PTR mean in DNS?
PTR stands for Pointer. A PTR record provides a hostname associated with a DNS reverse lookup name, usually derived from an IP address.
Can I look up PTR records for IPv6 addresses?
Yes. IPv6 supports reverse DNS through the ip6.arpa namespace. A lookup service must support IPv6 address validation and PTR queries to provide these results.
What happens if an IP address has no PTR record?
The reverse lookup may return no PTR answer. This does not automatically mean the IP address is invalid, disconnected, or unavailable.
Can a PTR record reveal the owner of an IP address?
Not reliably. It may identify a hostname associated with a network or hosting service, but the result is not proof of ownership or administrative control.
Are PTR records required for websites?
No. A website can generally operate without a PTR record for its hosting IP address. Reverse DNS is more relevant in certain email, server management, and network diagnostic situations.
Can I create a PTR record in my domain’s DNS panel?
Not necessarily. The reverse DNS zone is normally controlled by the IP address provider or an authorized delegate. Ask your hosting provider or ISP how reverse DNS is managed for the address.
Check Your Reverse DNS Configuration
A PTR lookup is a useful first check when investigating server hostnames, email delivery configuration, or unexpected DNS behavior.
Start with the correct public IP address, inspect the returned PTR hostname, and use a forward DNS check if you need to confirm whether the hostname resolves back to that address.
Remember that reverse DNS is one piece of information about an IP address. It does not establish identity, guarantee email delivery, or measure internet connection performance.