MyIPScan
Public PTR lookup

Reverse DNS / PTR Lookup

Check whether a public IP address has PTR records. Reverse DNS can suggest a hostname associated with an IP, but PTR records are optional and may be generic or outdated.

Look up PTR records

Enter a public IP address to start.
Technical response details (optional) 

        

      





  

    

      
Direct answer

      
Reverse DNS / PTR Lookup: answer first

      
Check reverse DNS PTR records for public IPv4 or IPv6 addresses. Use the result as an observable public-signal check with stated limitations, not as an absolute guarantee.

    

    

      Last updated
      
    

  





      
    

  





  

    
B2B diagnostic report model

    
Domain intelligence diagnostics

    
Domain checks connect public DNS, RDAP-safe context, reverse DNS, CAA, DNSSEC hints, IP/ASN context, provider hints, and blacklist context.

  

  

    
SummaryStart with a plain-language status for the public target.

    
Top issuesPrioritize the few findings that need attention first.

    
What passedShow expected public signals without turning them into a certification.

    
What needs reviewSeparate limited, unavailable, and review-worthy signals.

    
Why it mattersExplain the business, delivery, crawl, or implementation impact.

    
Recommended fixesPoint to the DNS, hosting, email, CMS, or SEO owner who can act.

    
What this tool cannot checkThis does not enumerate subdomains, scan ports, prove ownership, prove origin IP exposure, or certify infrastructure security.

    
Client-safe copyClient-safe copy should keep high-level DNS/RDAP/provider findings while suppressing raw payloads and RDAP contact personal data.

    
Monitoring beta (optional)Optional monitoring beta can compare DNS, RDAP status, expiration windows, provider hints, reverse DNS, and blacklist context for approved public domains.

  

  

    

      
Client-safe report

      
Share findings without leaking raw technical material

      
Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.

    

    

      Review Safe Copy
      Ask about monitoring beta
    

  

  

    Domain Intelligence ReportDomain intelligence diagnostics follow-up.
      Email Deliverability DoctorDomain intelligence diagnostics follow-up.
      Website Exposure ScannerDomain intelligence diagnostics follow-up.
      AI/Search Visibility ScannerDomain intelligence diagnostics follow-up.
  







  

    

      
Check my website/domain

      
What this checks

      
Public DNS, HTTP, HTTPS, certificate, redirect, header, IP/ASN, or domain configuration signals.

    

    

      
Limits

      
What this cannot check

      
It cannot perform credentialed vulnerability testing, scan private hosts, bypass access controls, or certify complete security.

    

    

      
Read results

      
How to use the output

      
Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.

    

  

  

    

      
Related tools

      
Continue with the closest checks

    

    

      Public Exposure ReportFull browser-session report with Safe Copy, issues, fixes, and clear limits.
      VPN Leak TestCompare visible IP, DNS, WebRTC, IPv6, and browser signals.
      Website Exposure ScannerHTTPS, redirects, headers, DNS, IPv6, mixed content, and CDN/origin context.
      Domain Intelligence ReportDNS inventory, RDAP-safe context, IP/ASN, provider hints, and blacklist context.
      MethodologyReview how MyIPScan labels signals, limitations, and Safe Copy output.
    

  







  

    
SEO and AI citation summary

    
Reverse DNS Lookup: what this tool does

    
Checks PTR records for public IPv4 and IPv6 addresses.

  

  

    

      
How to use

      
  1. Enter one public domain, IP address, or ASN value supported by the tool.
  2. Review record values, TTLs, provider hints, and confidence notes before changing DNS.
  3. Retest after propagation and compare with the Domain Intelligence Report.

    

    

      
What the result means

      
Treat DNS, RDAP, PTR, CAA, and provider context as public registry or resolver evidence. DNS can be cached, delegated, proxied, or incomplete.

    

    

      
Limitations

      
  • This tool reports observable signals only; it is not a guarantee or certification.
  • Uses /api/reverse-dns backed by Cloudflare DoH.
  • Results can change after VPN reconnects, DNS propagation, browser updates, cache changes, or provider configuration changes.

    

  

  

    
Reverse DNS Lookup — Common Questions

    

      What is a PTR record and what does it tell you?
      
A PTR (pointer) record maps an IP address back to a hostname — the reverse of an A record. PTR records are set by the IP address owner (usually the ISP or hosting provider) and stored in the in-addr.arpa zone. For example, the IP 8.8.8.8 has a PTR record of "dns.google". PTR records are used to identify servers, verify email sending IPs, and debug network connections.

    

    

      Why is PTR lookup important for email deliverability?
      
Many mail servers check that the sending IP has a matching PTR record (forward-confirmed rDNS). The PTR should resolve to a hostname, and that hostname's A record should resolve back to the same IP. If the PTR is missing or doesn't match, receiving servers often mark the email as spam or reject it. If you run your own mail server, setting a PTR record on your server's IP is one of the most important deliverability steps.

    

    

      My IP has no PTR record — is that a problem?
      
For home/residential IPs: no PTR is normal and not a problem for general browsing. For mail servers: missing PTR is a significant problem that will cause email to be rejected or sent to spam. For VPN or hosting IPs: no PTR can be a flag for security tools that check IP reputation. To add a PTR record, contact your IP address provider (ISP or hosting company) — you cannot set it yourself in your domain's DNS, only the IP block owner can.

    

    

      What does it mean if the PTR hostname doesn't match the IP (forward-confirmed rDNS fail)?
      
Forward-confirmed rDNS (FCrDNS) means: IP → PTR lookup → hostname → A record lookup → should match the original IP. If the A record of the PTR hostname points to a different IP, it fails FCrDNS. This is treated as suspicious by email servers and security tools. It usually means the PTR was set incorrectly, or the A record of the hostname was changed without updating the PTR. Fix both to match.

    

  

  

    
Next checks and references

    
DNS and Domain ToolsParent hub for this tool category.Domain Intelligence ReportLive DNS, RDAP, IP/ASN, PTR, CAA, DNSSEC, TXT, and provider hint report.DNS LookupDNS records through Cloudflare DoH.WHOIS / RDAP LookupPublic RDAP registry lookup.ASN LookupASN and network prefix lookup.Relevant guideBackground reading for interpreting this result.MethodologyHow MyIPScan labels confidence, limits, and safe-copy outputs.