Free PTR record lookup
Reverse DNS Lookup
Enter an IP address to find the hostname behind it, or a hostname to check the reverse DNS of every IP it uses. Built for checking mail servers.
Free, no sign-up. We only read public DNS records and do not keep what you check.
Result look wrong, or not sure what to change? A GoProIT technician can check it with you over a secure remote session. $59 per fix, Monday to Friday 8am to 8pm Eastern.
Book a technician(844) 734-1288What reverse DNS is
Normal DNS turns a name into an IP address. Reverse DNS does the opposite: it turns an IP address back into a name, using a PTR record. For example, Google’s resolver 8.8.8.8 has the PTR name dns.google.
Forward-confirmed reverse DNS (FCrDNS) means the round trip works both ways: the IP’s PTR name has an A or AAAA record that points back to the same IP. Mail servers check this to judge whether a sending server is properly set up.
Why reverse DNS matters for email
Google’s sender guidelines require every sending IP to have a valid PTR record that matches its forward DNS, and most other mail providers check it too. A server without one, or with a generic name like 203-0-113-10.dsl.example.net, looks like an infected home computer, so its mail is rejected or sent to spam.
If you send through Microsoft 365 or Google Workspace, their servers already have correct reverse DNS and you don’t need to do anything. This matters when you run your own mail server, send from a VPS or website, or a copier or app sends email directly from your office connection.
How to set a PTR record
Reverse DNS is controlled by whoever owns the IP address, not by your domain’s DNS host. To change it:
- VPS or cloud server: look for a reverse DNS or PTR setting in the provider’s control panel (Hostinger, DigitalOcean, AWS, Azure and others all have one).
- Business internet with a static IP: ask your ISP’s business support to set the PTR to your mail server’s name.
- Then add a matching A record in your own DNS, for example
mail.yourcompany.compointing to that IP, so the check passes both ways.
How to read the reverse DNS results
An rDNS check ends in one of four situations. Here’s what each one means for a server that sends email.
| Result | What it means | What to do |
|---|---|---|
| PTR found, forward-confirmed | The IP has a name, and that name points back to the same IP. | Nothing. This is what mail providers want to see. |
| PTR found, not confirmed | The IP has a name, but that name has no A or AAAA record, or it points to a different IP. | Add or fix the A record for the PTR name in your own DNS. |
| Generic PTR | The name is an ISP default, such as one with dsl, dynamic or the IP digits in it. | Fine for browsing. For a mail server, ask the IP owner to set a custom name. |
| No PTR | Nobody has set a reverse record for this IP. | Ask your ISP, host or cloud provider to add one if the IP sends email. |
The PTR name doesn’t have to contain your email domain. mail.yourcompany.com is tidy, but a name like server1.yourhost.net passes too, as long as it resolves back to the same IP. It’s also good practice for the PTR name to match the name the server announces when it connects to send mail (the HELO or EHLO name).
How to do a reverse DNS lookup from the command line
You can run the same check on any computer. All of these use Google’s resolver, 8.8.8.8, as the example, and should return dns.google.
- Windows Command Prompt:
nslookup 8.8.8.8. The name appears on the Name line. - Windows PowerShell:
Resolve-DnsName 8.8.8.8. PowerShell sees that it’s an IP and looks up the PTR record on its own. - Mac or Linux Terminal:
dig -x 8.8.8.8 +short, orhost 8.8.8.8.
To finish the forward-confirmed check by hand, look up the name you got back: nslookup dns.google. If the original IP is in the answer, the round trip works.
Behind the scenes, a reverse lookup reverses the IP and adds a special domain. A lookup for 203.0.113.10 is really a query for the PTR record of 10.113.0.203.in-addr.arpa. IPv6 works the same way under ip6.arpa, one hex digit at a time, which is why those names are so long. That zone belongs to whoever was assigned the IP block, which is why your own DNS host can’t change it.
Email errors caused by missing reverse DNS
When reverse DNS is the problem, the bounce message usually says so. These are the ones that come up most on small business mail servers and devices.
- Gmail: 550 5.7.25. Gmail says the sending IP has no PTR record, or its forward record doesn’t point back to that IP, and that it doesn’t accept mail from IPs without one.
- Other providers: wording such as “Client host rejected: cannot find your hostname” or “reverse DNS lookup failed” means the same thing.
A typical office example
A copier is set up to scan to email by sending straight from the office’s internet connection. Scans to staff work, because they go through Microsoft 365. Scans sent to an outside accountant bounce with 550 5.7.25, because the office IP has the ISP’s generic PTR name. The quickest fix is usually not reverse DNS at all. Point the copier at Microsoft 365 or Google Workspace as its SMTP server, so the mail leaves from their properly configured servers. Ask the ISP for a custom PTR only if you really run your own mail server.
Other uses for a reverse IP lookup
Reverse DNS also helps you identify an unknown IP in a log. If a Microsoft 365 sign-in report shows a login from an IP you don’t recognize, the PTR name often tells you whether it belongs to a home broadband provider, a mobile carrier or a hosting company. A sign-in from a hosting company’s IP for a regular office user is worth investigating. Remember that the IP owner chooses the PTR name, so treat it as a clue, not proof. The what is my IP tool shows your own office IP, and the blacklist check tells you whether a sending IP has also landed on spam lists. If you’d rather not deal with the ISP or the server yourself, a technician can check reverse DNS, SPF and DKIM together over a remote session for $59.
Frequently asked questions
Can I set reverse DNS in my domain’s DNS settings?
No. PTR records live in a special zone owned by the company that controls the IP address block. Only your ISP, hosting company or cloud provider can set them. You control the forward A record that should match.
Does my website need reverse DNS?
No. Visitors’ browsers never check it. Reverse DNS matters for servers that send email and for some security and logging tools.
Why does my IP have a generic PTR name?
ISPs give every address a default name that includes the IP, often with words like dsl, dynamic or pool. That is fine for browsing, but spam filters treat mail from such names as suspicious. Ask for a custom PTR if the IP sends email.
Does this tool support IPv6?
Yes. Enter an IPv6 address directly, or a hostname with AAAA records, and the tool checks the ip6.arpa reverse records as well.
What is an rDNS check?
An rDNS check looks up the PTR record of an IP address to find its hostname, then usually confirms that the hostname points back to the same IP. Mail servers run it on every incoming connection to judge whether the sender is a properly configured server.
How long does a new PTR record take to work?
Once your ISP or host saves it, most resolvers see it within minutes to a few hours, depending on the TTL they set. If the old PTR was cached by a mail provider, allow up to a day before retrying.
Can one IP address have more than one PTR record?
Technically yes, but don’t do it for a mail server. Mail servers may only check one of the names, and multiple PTRs make the forward check unpredictable. Use one PTR name per sending IP.
Why does a reverse DNS lookup return nothing?
Either no PTR record has been set for that IP, or the IP is a private address such as 192.168.1.20 or 10.0.0.5, which has no public reverse DNS. Private addresses can only be looked up on your own network’s DNS server, if it has a reverse zone.
Related guides
- Emails going to spam: how to fix it
- Sending email through Gmail SMTP with an app password
- Email authentication failed: causes and fixes
Get help from a technician
More free tools
DNS & websiteDNS LookupSee every DNS record for a domain or hostname: A, MX, TXT, CNAME, NS and more.Open tool
DNS & websiteDNS Propagation CheckerCompare your nameservers with 10 public resolvers to see if a DNS change has spread.Open tool
DNS & websiteSSL Certificate CheckerCheck a website's SSL certificate: expiry, names covered, chain and TLS version.Open tool
DNS & websiteWHOIS Lookup & Domain Expiry CheckRegistrar, expiry date, nameservers and transfer lock for any domain.Open tool
DNS & websiteWebsite Security CheckGrade a website on HTTPS, SSL, security headers, cookies and outdated software.Open tool
Email & domainEmail Domain Health CheckOne check for MX, SPF, DKIM, DMARC and blocklists, with a score out of 100 and a fix list.Open tool
Email & domainMX Record LookupSee which mail servers receive email for a domain, their priority, IPs and provider.Open tool
Email & domainSPF Record Checker & GeneratorValidate your SPF record, count the 10-lookup limit and build a new record.Open tool Free tools find it. We fix it.
Want a technician to sort it out for you?
One-time remote fix for $59, or unlimited help for your whole team at $49 per user per month. No contract and no setup fee.