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.

Sources: the reverse zone's nameservers, reached from a root server · Google Public DNS · Cloudflare 1.1.1.1 · Team Cymru

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.

Anatomy of a reverse namelive 2026-10-23

IPv4 addressOpenDNS

208.67.222.222222.222.67.208.in-addr.arpa

Its reverse name, asked for PTRresolver1.opendns.com +3

Octets reversedThe /8 comes last: 208.in-addr.arpa is ARIN's zone, 222.67.208.in-addr.arpa OpenDNS's own.
in-addr.arpaThe IPv4 reverse tree, administered by IANA and served by a to f.in-addr-servers.arpa.
PTRWhat the name holds: resolver1.opendns.com and three more hostnames.

IPv6 address, written out in fullGoogle

2001:4860:4860:0000:0000:0000:0000:8888

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.

8.8.8.8.in-addr.arpaIPv4: four labels, reversed
8.8.8.8.0.0.0.0…ip6.arpaIPv6: all 32 digits, reversed
8.8.8.8.0.6.8.4…ip6.arpa:: left compressed: another name, and NXDOMAIN
8.8.8.8 reads the same both ways, so the figure uses 208.67.222.222, whose octets visibly swap places. The tool's reverse path draws the same swap for every IPv4 address it looks up.

How 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 +answer

dig builds 8.8.8.8.in-addr.arpa itself. The number before IN is the TTL your resolver has left.

Reading dig's answerGoogle Public DNS, then Google's own server · recorded 2026-10-23
bash · zsh
$ 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)
  1. Status. NOERROR with one answer. NXDOMAIN would mean no PTR is set; SERVFAIL, a broken reverse zone.
  2. The question. dig built 8.8.8.8.in-addr.arpa from the address and asked for its PTR.
  3. TTL. 14,003 seconds left in Google's cache. The zone's own server gives the full 86,400, one day.
  4. The hostname. The PTR's value. The trailing dot ends the name.
  5. Who answered. 8.8.8.8, a cache. In the second answer the aa flag marks the zone's own server.
One PTR, asked twice: Google Public DNS answers from its cache, counting down; ns1.google.com, asked with +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.

Reverse DNS lookup of 8.8.8.8: PTR record dns.google from Google's nameserver, its forward check and the delegation pathReverse DNS lookup of 8.8.8.8: PTR record dns.google from Google's nameserver, its forward check and the delegation pathThe 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.
A reverse DNS lookup of 8.8.8.8: the verdict, the PTR record with its TTL and forward check, and the reverse path from the root to Google's zone. Select a number to see what each part shows.

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.

One name, two zones8.8.8.8 and dns.google, live 2026-10-23
Forward zonethe domain's: dns.google
dns.google. A 8.8.8.8dns.google. A 8.8.4.4dns.google. AAAA 2001:4860:4860::8888dns.google. AAAA 2001:4860:4860::8844

Served by ns1.zdns.google for the holder of dns.google

two zones, two sets of servers
Reverse zonethe address block's: 8.8.8.0/24
8.8.8.8.in-addr.arpa. PTR dns.google.

Delegated by ARIN to Google, served by ns1.google.com

8.8.8.8.in-addr.arpa.Reverse name86400TTL · 1 dayINClassPTRTypedns.google.Hostname
1 address, 4 names208.67.222.222: resolver1.opendns.com and three more
1 address, 48 names17.253.144.10, apple.com's address, each with a 5-minute TTL
1 name, 4 addressesdns.google: 8.8.8.8, 8.8.4.4 and two IPv6
The PTR says what 8.8.8.8 is called; the A records say where dns.google points. Google happens to run both zones, on different servers.

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.

Three addresses, three loopslive 2026-10-23
Forward-confirmedGoogle
8.8.8.8dns.google8.8.8.8: same address
Points backdns.google also returns 8.8.4.4
Points elsewhereAdGuard
94.140.14.14dns.adguard-dns.com185.113.30.30: another address
Not confirmedits A record is 185.113.30.30
No PTRCloudflare
104.18.0.1NXDOMAIN: no name
Nothing to confirmNXDOMAIN from Cloudflare's zone
The same loop runs up the right edge of every result: green when the name leads back, amber when it leads elsewhere.

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.

Required, recommended, not statedeach receiver's own page, checked 2026-10-23
CheckGmailsender guidelinesYahoo Mailsender best practicesOutlook.compostmaster policy
Has a PTR recordrequiredrequiredrequired
The name points backrequiredrequirednot stated
Not generic or dynamicnot statedrecommendsmay refuse dynamic IPs
Four real senders, checked live
mail-sor-f41.google.com209.85.220.41 · Gmail's own outbound serverpasspasspass
ec2-3-80-0-1.compute-1.amazonaws.com3.80.0.1 · AWS's default namepasspasswarningpasswarning
dns.adguard-dns.com94.140.14.14 · points to 185.113.30.30failfailpass
No PTR104.18.0.1 · NXDOMAINfailfailfail

Gmail's replies

421 4.7.0 · 451 4.7.23Rate limited: no PTR, or its forward entry doesn't match the sending IP
550 5.7.25Blocked: no PTR, or the forward entry doesn't reference the sending IP
550-5.7.1Over IPv6: the message doesn't meet the IPv6 sending guidelines for PTR records and authentication
Only requirements fail. Yahoo's recommendation and Outlook.com's dynamic-IP warning show as warnings. Gmail's codes are from its SMTP error reference.

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.

Who hands the zone downrecorded walks, 2026-10-23
  1. in-addr.arpaAdministered by IANA, served by a to f.in-addr-servers.arpa
  2. 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
  3. 8.8.8.in-addr.arpaThe holder of 8.8.8.0/24: Google writes the PTR, on ns1 to ns4.google.com
17.in-addr.arpaA legacy /8, delegated by in-addr.arpa straight to Apple's own servers
129.2.0.192.in-addr.arpa CNAME 129.128/26.2.0.192.in-addr.arpaRFC 2317's own example: for a block under 256 addresses, the parent zone holds a CNAME into a zone the block's holder runs. The child zone's name is only a convention.
Each hop is a referral recorded on 2026-10-23, except RFC 2317's, which is the RFC's own example on a documentation block.
Where each provider sets the PTReach provider's own documentation, checked 2026-10-23
ProviderHow to set itLimits
AWSDocumentationElastic 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 AzureDocumentationSet 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 CloudDocumentationVerify 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.
HetznerDocumentationCloud: 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.
DigitalOceanDocumentationThere 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.
OVHcloudDocumentationPoint 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.
VultrDocumentationProducts › 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)DocumentationAdd 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 CloudDocumentationCreate 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 8501Ask 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.
How long a change takes: until caches drop the old PTR (its TTL) or the cached “no PTR” answer (RFC 2308). Live TTLs: 1 day for 8.8.8.8, 7 days for resolver1.opendns.com, 5 minutes for an EC2 default name.

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.

One PTR per address, at IPv4 and IPv6 scaleRFC 8501
/24one IPv4 block28 = 256
/64one IPv6 subnet264 = 18,446,744,073,709,551,616
/48one IPv6 site280 = 1,208,925,819,614,629,174,706,176

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

NXDOMAINno nameNo PTR at all: the most accurate answer, but mail servers are likely to refuse such senders.
A wildcarddoesn't matchOne name for a whole prefix: its forward lookup can't lead back to every address.
Dynamic DNSmatchesEach host sends its own AAAA and PTR updates once its address is set.
Delegate the zoneup to the customerCustomers who run DNS servers get their prefix's reverse zone; most homes can't.
On the flymatchesThe server makes a PTR when asked, with the matching AAAA.

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.

Two lookups decide it66.249.66.1, live 2026-10-23
  1. Reverse lookupThe PTR of the visiting address.66.249.66.1 → crawl-66-249-66-1.googlebot.com
  2. Google's domain?It ends in googlebot.com. A googleusercontent.com name would also need the address in Google's lists.
  3. Forward lookupcrawl-66-249-66-1.googlebot.com → 66.249.66.1Same address: a real Googlebot.
A fake: “Googlebot” in the user agent, from 203.0.113.9Its reverse lookup answers NXDOMAIN, so the check stops at step 1. (A documentation address, RFC 5737.)
CrawlerPTR name ends inPublished IP list
GooglebotPTR and forward lookup, or the listgooglebot.comcommon-crawlers.json
Google special-case crawlersPTR and forward lookup, or the listrate-limited-proxy-….google.comspecial-crawlers.json
Google user-triggered fetchersPTR and forward lookup, or the listgoogle-proxy-….google.com….gae.googleusercontent.comonly with the listuser-triggered-fetchers-google.jsonuser-triggered-fetchers.jsonuser-triggered-agents.json
BingbotPTR and forward lookup, or the listsearch.msn.combingbot.json
ApplebotPTR and forward lookup, or the listapplebot.apple.comapplebot.json
YandexBotPTR and forward lookupyandex.ruyandex.netyandex.comnone
DuckDuckBotIP list onlynoneduckduckbot.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

Domains and lists from each operator's own page, checked 2026-10-23. Bing asks that its list be refreshed daily.

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.

Each answer, a real examplelive 2026-10-23
NOERROR8.8.8.8A name is set: the PTR comes back with its TTL.PTR dns.google. · TTL 86400ns1.google.com · aa
NXDOMAIN104.18.0.1No such name: Cloudflare's zone holds no PTR for it, and says so.SOA 18.104.in-addr.arpacruz.ns.cloudflare.com … 3600
NODATANOERROR, 0 answers2001:4860:4860::/48The name exists, without a PTR: the name of Google's /48, which has names below it.0.6.8.4.0.6.8.4.1.0.0.2.ip6.arpaSOA ns1.google.com … 60
SERVFAIL203.0.113.50made up, documentation addressLame delegation: the registry names two servers that don't serve the zone, so resolvers give up.APNIC → ns1, ns2.example.net: lameEDE 22: No Reachable Authority
NXDOMAINAS112192.168.1.1A private address: the public tree hands 168.192.in-addr.arpa to IANA's AS112 servers, which answer NXDOMAIN.blackhole-1.iana.orgSOA prisoner.iana.org … 604800
A “no” is cached for the SOA's negative time (RFC 2308): 1 hour at Cloudflare, 60 seconds at Google, 7 days from AS112.

Reverse DNS lookup: frequently asked questions

What is a reverse DNS lookup?

A reverse DNS lookup finds the host name behind an IP address by reading its PTR record, the opposite of a normal lookup that turns a name into an address. The address is reversed into a special name, such as 8.8.8.8.in-addr.arpa, and asked of the nameservers that hold it. For 8.8.8.8 the answer is dns.google. This tool also checks that the name points back.

How do I check a PTR record with dig or nslookup?

Run dig -x 8.8.8.8 on macOS or Linux: dig reverses the address itself and the PTR appears in the answer section. On Windows, nslookup 8.8.8.8 prints it on its Name: line. To skip every cache, ask the zone's own nameserver: dig -x 8.8.8.8 @ns1.google.com +norecurse. The Commands view here fills in each command with your address and its zone's server.

Why does my IP address have no reverse DNS?

Because nobody has set a PTR record for it. Only the holder of the address block can, so the answer is NXDOMAIN until your hosting provider or ISP adds one. Most home connections and most IPv6 addresses have none. If the lookup shows SERVFAIL instead, the reverse zone itself is broken, usually a lame delegation the provider must fix.

How do I set up or change a PTR record?

At whoever gave you the address. On AWS, publish the forward A record first, then update the Elastic IP's reverse DNS. Azure sets ReverseFqdn on the public IP, DigitalOcean uses the Droplet's name, Hetzner, OVHcloud, Vultr and Linode have an rDNS field beside each address. For a home or office line, ask your ISP: usually only business plans with a static IP qualify.

How long does a PTR record change take?

As long as caches keep the old answer. Each resolver may serve the old PTR until its TTL runs out, often one hour to one day, or the cached "no PTR" answer for the zone's negative-cache time. There is no fixed 24 to 48 hours. The Copies view shows how much time Google's and Cloudflare's copies have left.

Can an IP address have more than one PTR record?

Yes. DNS allows several PTR records for one address, and RFC 2181 says no limit should be assumed: 208.67.222.222 has four. Mail checks pass when any of them points back to the address. Some tools read only the first name, so the one you use for mail should be forward-confirmed. One PTR is the simplest setup, not a requirement.

What is FCrDNS?

Forward-confirmed reverse DNS: the PTR's name, looked up forward, returns the same address. 8.8.8.8 reverses to dns.google, and dns.google resolves to 8.8.8.8, so it passes. Mail servers call the check iprev. It matters because anyone holding an address can write any name into its PTR; only the forward lookup shows the domain's owner agrees.

Do I need reverse DNS to send email?

Yes, for any server that sends mail directly. Gmail requires every sending IP to have a PTR that resolves back to it, Yahoo requires valid forward and reverse DNS, and Outlook.com requires valid reverse DNS. Without one, mail is rate-limited or rejected, for example with Gmail's 550 5.7.25. A generic provider name passes the rules but draws warnings.

What does "reverse DNS is not a valid hostname" mean?

Mail server tests print it when the sending IP's PTR name doesn't work as a host name for that IP: most often there is no PTR at all, or the name has no A record pointing back to the same address. Look up the sending IP here: the PTR view shows the name and its forward check, and the Mail view names the rule it breaks.

Is reverse DNS the same as a reverse IP lookup?

No. Reverse DNS reads the name or names the address's holder published in its PTR records. A reverse IP lookup tries to list every website hosted on an address, which needs passive DNS data collected from many resolvers over time. Many sites use the two terms loosely. Our IP to Hostname page explains what each method can find.

Does reverse DNS work with IPv6?

Yes. IPv6 addresses are looked up under ip6.arpa with all 32 hex digits reversed, so 2001:4860:4860::8888 gives a 32-label name that this tool builds and asks for you. Most IPv6 addresses have no PTR, because ISPs can't pre-fill names for so many addresses, but servers that send mail over IPv6 need one.

Why does a private IP address have no PTR?

Private addresses such as 192.168.1.1 or 10.0.0.1 are used inside many networks at once, so the public DNS can't name them. Their reverse lookups belong to your own network's resolver; those that leak out end at the AS112 servers, which answer that no such name exists. The tool explains each special-use range with its RFC without asking anyone.

Missing something?Suggest a feature or a new tool