Reverse DNS Lookup
Find the hostname behind any IPv4 or IPv6 address: every PTR record straight from the reverse zone's own nameservers, whether each name points back to the address (FCrDNS), who runs the zone, and whether it passes Gmail's, Yahoo's and Microsoft's rules for mail servers.
IPv4 or IPv6 in any notation, a hostname (resolved first) or an in-addr.arpa name.
What is reverse DNS (rDNS)?
Reverse DNS turns an IP address back into a host name: the opposite of the usual (forward) lookup, which turns a name into an address. The answer is a PTR record that the address's holder publishes in a part of DNS kept for addresses.
DNS names are read from right to left, so an address is written backwards to be looked up: 8.8.8.8 becomes 8.8.8.8.in-addr.arpa and 203.0.113.7 becomes 7.113.0.203.in-addr.arpa. With the network's part on the right, each block of addresses can be handed to whoever holds it (RFC 1035 §3.5).
IPv6 uses ip6.arpa and all 32 hex digits (nibbles) of the address, last digit first: :: is expanded before the digits are reversed, so 2001:4860:4860::8888 has a 32-label name (RFC 3596 §2.5). The tool shows the name it will ask under the field as you type, and writes out all 32 nibbles in the reverse path beside the result.
IPv4 addressOpenDNS
Its reverse name, asked for PTRresolver1.opendns.com +3
IPv6 address, written out in fullGoogle
2001:
32 nibbles, last digit first
The 8888 at the end comes first, Google's 2001:4860 /32 comes last, and the 16 zeros that :: hid are written out.
:: left compressed: another name, and NXDOMAINHow to do a reverse DNS lookup
Type an address above and press Look up PTR. The tool walks down from a root server to the reverse zone's own nameserver and asks it directly, then compares Google's and Cloudflare's cached copies. From a terminal, dig -x 8.8.8.8 on macOS and Linux, nslookup 8.8.8.8 on Windows, or host 8.8.8.8 all do the same.
dig -x builds the in-addr.arpa or ip6.arpa name for you; add @ and the zone's nameserver with +norecurse (dig -x 8.8.8.8 @ns1.google.com +norecurse) to read the zone's own answer and its full TTL instead of a cache. For PowerShell, Microsoft's documented form passes the reversed name: Resolve-DnsName -Name 8.8.8.8.in-addr.arpa -Type PTR.
dig -x 8.8.8.8 +noall +answerdig builds 8.8.8.8.in-addr.arpa itself. The number before IN is the TTL your resolver has left.
$ dig -x 8.8.8.8 @8.8.8.8 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24160 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; QUESTION SECTION: ;8.8.8.8.in-addr.arpa. IN PTR ;; ANSWER SECTION: 8.8.8.8.in-addr.arpa. 14003 IN PTR dns.google. ;; SERVER: 8.8.8.8#53(8.8.8.8) $ dig -x 8.8.8.8 @ns1.google.com +norecurse ;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 8.8.8.8.in-addr.arpa. 86400 IN PTR dns.google. ;; SERVER: 216.239.32.10#53(216.239.32.10)
- Status. NOERROR with one answer. NXDOMAIN would mean no PTR is set; SERVFAIL, a broken reverse zone.
- The question. dig built 8.8.8.8.in-addr.arpa from the address and asked for its PTR.
- TTL. 14,003 seconds left in Google's cache. The zone's own server gives the full 86,400, one day.
- The hostname. The PTR's value. The trailing dot ends the name.
- Who answered. 8.8.8.8, a cache. In the second answer the
aaflag marks the zone's own server.
+norecurse, answers for the zone with the full TTL.How to read the result
The head says in one sentence what the address reverses to and whether the name points back, with the zone's TTL and the server that answered. Tinted notes below it say who can change the name and what is unusual about it.
The PTR view lists every name with its TTL and forward check; Mail scores it against the receivers' rules; Delegation shows each server asked; Copies compares Google's and Cloudflare's cached answers; Commands gives the same lookup for a terminal. On the right, the reverse path draws the whole walk.

The verdictWhat the address reverses to, whether that name points back, and who set it, with the TTL and the answering server.The PTR recordsEvery name the zone holds for the address, with its TTL and the addresses its forward lookup returns.The viewsMail rules, the delegation hop by hop, the cached copies with their countdowns, and the commands.The reverse pathThe address reversed into its DNS name, then the root, IANA, the registry and the zone that answered.What is a PTR record?
A PTR (pointer) record, DNS type 12, holds one host name for the address it sits under: 8.8.8.8.in-addr.arpa. 86400 IN PTR dns.google. It is plain data: unlike a CNAME, it sends nothing anywhere else (RFC 1035 §3.3.12).
The address's holder writes it, not the owner of the name inside it: Google's reverse zone says 8.8.8.8 is dns.google, and only the A record in the dns.google zone says the reverse. One address can carry several PTR records (RFC 2181 §10.2): 208.67.222.222 has four. The name must be a real host name, never an alias.
A PTR holds a name and nothing else: no owner, country or city. A place shown beside a lookup comes from words the operator put in the name, or from a separate database.
Served by ns1.zdns.google for the holder of dns.google
Delegated by ARIN to Google, served by ns1.google.com
What is forward-confirmed reverse DNS (FCrDNS)?
Forward-confirmed reverse DNS means the PTR's name resolves back to the same address: 8.8.8.8 → dns.google → 8.8.8.8. Mail servers call the check iprev (RFC 8601 §3): look up the address's PTR names, look up each name's A or AAAA records, and pass when the address is among them.
The second step matters because whoever holds an address can write any name into its PTR, google.com included. The name proves something only when the domain's owner points it back. The tool checks every PTR name, up to ten, and draws the loop on the right: green when it closes, amber when the name points somewhere else.
With several PTR records, one that points back is enough. A name whose A record lists other addresses as well still passes, as long as this address is one of them.
Reverse DNS check for mail servers: what Gmail, Yahoo and Outlook.com require
All three want a PTR record on every sending IP. Gmail also requires the name to resolve back to the same IP, and Yahoo requires "a valid forward and reverse DNS record", both for every sender since February 2024. Outlook.com's policy asks for valid reverse DNS and says nothing about the forward step.
A generic name such as ec2-3-80-0-1.compute-1.amazonaws.com fails no rule: Yahoo only recommends a meaningful, non-generic name that reflects your domain. Outlook.com warns that connections from dynamic IP space may not be accepted, which hits an ISP's pool names, not a cloud server's static default. The Mail view shows those as warnings and the requirements as pass or fail; a check that couldn't finish is neither.
Two things are never failures: several PTR records, which RFC 2181 allows, and a PTR that differs from the server's HELO name: RFC 5321 §4.1.4 says a server must not refuse mail for that. Gmail rate-limits with 421 4.7.0 or 451 4.7.23 and blocks with 550 5.7.25 when the PTR is missing or doesn't point back.
| Check | Gmailsender guidelines | Yahoo Mailsender best practices | Outlook.compostmaster policy |
|---|---|---|---|
| Has a PTR record | required | required | required |
| The name points back | required | required | not stated |
| Not generic or dynamic | not stated | recommends | may refuse dynamic IPs |
| Four real senders, checked live | |||
| mail-sor-f41.google.com209.85.220.41 · Gmail's own outbound server | pass | pass | pass |
| ec2-3-80-0-1.compute-1.amazonaws.com3.80.0.1 · AWS's default name | pass | passwarning | passwarning |
| dns.adguard-dns.com94.140.14.14 · points to 185.113.30.30 | fail | fail | pass |
| No PTR104.18.0.1 · NXDOMAIN | fail | fail | fail |
Gmail's replies
Who controls reverse DNS, and how to set a PTR record
The holder of the address block, never the owner of a domain. IANA delegates each block's reverse zone to its Regional Internet Registry, and the registry to the network holding the addresses, which runs the zone or hands it on (RFC 3172). Owning example.com doesn't let you name an address: your host or ISP must.
Clouds let customers set it, each with its own rule: AWS wants the forward A record first, Azure sets IPv4 only and not in its portal, DigitalOcean builds the PTR from the Droplet's name, Google Cloud asks you to prove the domain. On a home line, usually only a business plan with a static IP gets a custom PTR: ask the ISP. Blocks smaller than a /24 are often handed on with CNAMEs (RFC 2317), which the tool follows wherever they point.
A change reaches everyone once caches drop the old answer: the old record's TTL decides, or the cached "no PTR" time when there was none (RFC 2308), not a fixed 24 to 48 hours. Vultr says its own changes take 6 to 12 hours.
- in-addr.arpaAdministered by IANA, served by a to f.in-addr-servers.arpa
- 8.in-addr.arpa · 208.in-addr.arpaThe block's regional registry: ARIN for 8.0.0.0/8 and 208.0.0.0/8ARINRIPE NCCAPNICLACNICAFRINIC
- 8.8.8.in-addr.arpaThe holder of 8.8.8.0/24: Google writes the PTR, on ns1 to ns4.google.com
| Provider | How to set it | Limits |
|---|---|---|
| AWSDocumentation | Elastic IPs only. Publish an A record for your name that points to the Elastic IP, then EC2 console › Elastic IPs › the address › Actions › Update reverse DNS, or aws ec2 modify-address-attribute --allocation-id … --domain-name mail.example.com. | The forward A record must exist first. While it has a reverse record, the Elastic IP is locked to your account. In GovCloud (US), only AWS Support can set one. Port 25 limits are lifted with a separate request. |
| Microsoft AzureDocumentation | Set the public IP's ReverseFqdn: az network public-ip update --resource-group RG --name PublicIp --reverse-fqdn mail.example.com. (the name ends with a dot), or Set-AzPublicIpAddress in PowerShell. | IPv4 only: Azure-owned IPv6 addresses get no PTR. Not in the Azure portal. The name must resolve to that IP or belong to your subscription. One PTR per address, none by default, and none for App Service or Application Gateway. |
| Google CloudDocumentation | Verify the domain first (Search Console, or an A record to the VM's external IP). Then VM instances › the instance › Edit › the primary network interface › Public DNS PTR record, or gcloud compute instances update-access-config INSTANCE --public-ptr --public-ptr-domain mail.example.com. | Primary network interface only; no PTR for load balancers or Cloud NAT. IPv6 PTRs need a dual-stack or IPv6-only subnet with external IPv6. The default name is <reversed-ip>.bc.googleusercontent.com. |
| HetznerDocumentation | Cloud: Hetzner Console › the server (or Primary IP, Floating IP) › Networking › edit rDNS beside the IP; for IPv6 enter only the interface part, such as ::1. Dedicated: Robot › the server › IPs, the box beside each IP. | Hetzner runs the reverse zone. It counts an rDNS entry as valid only when it resolves both ways (FCrDNS). The default is static.<reversed-ip>.clients.your-server.de. |
| DigitalOceanDocumentation | There is no PTR editor: name or rename the Droplet with the full name you want, such as mail.example.com, and DigitalOcean creates the PTR from it. | The name must be a valid FQDN (my-droplet gives no PTR). Only the Droplet's first IPv6 address gets a PTR. PTRs can't be created by hand. |
| OVHcloudDocumentation | Point an A or AAAA record at the IP first. Then Control Panel › Network › Public IP Addresses › the actions button on the IP's row › Configure the reverse DNS (Public Cloud: your project › Public IPs). | OVHcloud checks at once that the name points back to the same IP, so the record must already be live. The name must be lower case and end with a dot. |
| VultrDocumentation | Products › Compute › the instance › Settings › IPv4 or IPv6 › Public Network: click the name in the Reverse DNS column, enter the full name and save. | Vultr asks that the name resolves back to the same IP, and says changes take 6 to 12 hours to show. The default is <ip>.vultrusercontent.com. |
| Akamai Cloud (Linode)Documentation | Add the A (and AAAA) record first. Then Cloud Manager › Linodes › the Linode › Network › the IP's ellipsis menu › Edit RDNS, and enter the full name; an empty field resets the default. | Fails with an error until the A record matches the IP. IPv6 ranges: Edit rDNS on the range, then each address. Defaults: <ip-with-dashes>.ip.linodeusercontent.com, older li<n>-<n>.members.linode.com. |
| Oracle CloudDocumentation | Create the A or AAAA record first, then open a service request with the IP, the name you want in the PTR and the forward record's name; Oracle checks it and creates the PTR. | One PTR per IP, by support request only; the forward record must resolve to that IP. |
| Your internet providerRFC 8501 | Ask your internet provider: only the provider, which holds the address, can set its PTR. In practice that takes a static IP on a business plan. | Home lines keep the provider's pool name, and receivers such as Comcast treat such names as dynamic and refuse direct mail from them. |
Why most IPv6 addresses have no PTR record
Because there are too many to name one by one. An ISP can pre-fill a PTR for every IPv4 address it hands out, but a single /48 holds 2⁸⁰ addresses, and devices pick their own, often short-lived (RFC 8501).
RFC 8501 lists the ISP's options: answer NXDOMAIN (no PTR, the most accurate), a wildcard PTR for each customer's prefix, dynamic DNS, delegating the zone to the customer, or generating matching PTR and AAAA records on the fly. Only the wildcard breaks the forward check; for home users a clean NXDOMAIN is fine, a timeout is not.
Servers that send mail over IPv6 still need a forward-confirmed PTR: Gmail rejects IPv6 mail without one with 550-5.7.1 Message does not meet IPv6 sending guidelines regarding PTR records and authentication. Azure gives its own IPv6 addresses no PTR at all.
Bar length: bits of address space. Each bit doubles the count.
At 1,000 PTR records a second, a /48 would still not be complete after 38 trillion years (RFC 8501).
RFC 8501's options for an ISP
A mail server still needs its own, forward-confirmed:2001:4860:4860::8888 → dns.google → 2001:4860:4860::8888
How to verify Googlebot and other crawlers
Look up the visitor's address, check that the PTR name ends in the crawler's documented domain, then look that name up forward and confirm it returns the same address: 66.249.66.1 → crawl-66-249-66-1.googlebot.com → 66.249.66.1. Or match the address against the operator's published list (Google's method).
The documented domains: googlebot.com and google.com for Google, search.msn.com for Bingbot, applebot.apple.com for Applebot, yandex.ru, yandex.net and yandex.com for Yandex. DuckDuckBot publishes only a list of addresses.
googleusercontent.com proves nothing alone: every Google Compute Engine VM gets a name under it by default, so the tool counts it as Google only when the address is in Google's published lists. A name with the right ending that doesn't point back is a fake, and the tool says so.
- Reverse lookupThe PTR of the visiting address.66.249.66.1 → crawl-66-249-66-1.googlebot.com
- Google's domain?It ends in googlebot.com. A googleusercontent.com name would also need the address in Google's lists.
- Forward lookupcrawl-66-249-66-1.googlebot.com → 66.249.66.1Same address: a real Googlebot.
| Crawler | PTR name ends in | Published IP list |
|---|---|---|
| GooglebotPTR and forward lookup, or the list | googlebot.com | common-crawlers.json |
| Google special-case crawlersPTR and forward lookup, or the list | rate-limited-proxy-….google.com | special-crawlers.json |
| Google user-triggered fetchersPTR and forward lookup, or the list | google-proxy-….google.com….gae.googleusercontent.comonly with the list | user-triggered-fetchers-google.jsonuser-triggered-fetchers.jsonuser-triggered-agents.json |
| BingbotPTR and forward lookup, or the list | search.msn.com | bingbot.json |
| ApplebotPTR and forward lookup, or the list | applebot.apple.com | applebot.json |
| YandexBotPTR and forward lookup | yandex.ruyandex.netyandex.com | none |
| DuckDuckBotIP list only | none | duckduckbot.json |
Live today, each pointing back:crawl-66-249-66-1.googlebot.commsnbot-157-55-39-1.search.msn.com17-58-101-179.applebot.apple.com
Reverse DNS errors explained
NXDOMAIN means the reverse name doesn't exist: nobody has set a PTR for the address. NOERROR with no answer (NODATA) means the name exists but holds no PTR. Resolvers keep either answer for the zone's negative-cache time from its SOA (RFC 2308), so a new PTR can take that long to show.
SERVFAIL means the zone is broken, most often a lame delegation: the servers named for the zone don't serve it, and every resolver gives up. REFUSED comes from a server that won't answer for the zone at all. Private and documentation addresses never get a public PTR: the tool answers them from IANA's registry without asking anyone.
Reverse DNS lookup: frequently asked questions
What is a reverse DNS lookup?
How do I check a PTR record with dig or nslookup?
Why does my IP address have no reverse DNS?
How do I set up or change a PTR record?
How long does a PTR record change take?
Can an IP address have more than one PTR record?
What is FCrDNS?
Do I need reverse DNS to send email?
What does "reverse DNS is not a valid hostname" mean?
Is reverse DNS the same as a reverse IP lookup?
Does reverse DNS work with IPv6?
Why does a private IP address have no PTR?
Missing something?Suggest a feature or a new tool
More DNS, IP and email tools
IP to Hostname
Convert IP addresses to hostnames via reverse DNS
DNS Lookup
Every DNS record from the domain's own nameservers, beside Google's and Cloudflare's cache
IP Lookup
Look up IP address geolocation, ISP, and network details instantly
MX Lookup
Find mail exchange records and mail server details
IP Blacklist Check
Check if an IP address is listed on spam or malware blacklists
SPF Record Checker
Validate SPF records and check DNS lookup count per RFC 7208
SMTP Test Tool
Test any mail server: STARTTLS, certificate, AUTH and open relay
Domain to IP
Convert any domain name to its IP address with geolocation and CDN detection