Check reverse DNS before IP reputation becomes the hidden risk.
Paste sending IPs and Lens checks PTR/rDNS, forward-confirmed rDNS, and public IP blacklist exposure. The result feeds the same KILL / REHAB / KEEP fix plan as the main estate scanner.
Why rDNS matters
Provider hygiene
Missing PTR makes infrastructure look unfinished or poorly controlled.
Forward confirmation
PTR that does not resolve forward to the IP can indicate sloppy or shared infrastructure.
IP context
Lens combines rDNS with public IP RBL exposure instead of treating DNS hygiene alone as clean.
How to act on the rDNS result
If PTR is missing
Set PTR at the hosting or ESP provider before using the IP for outbound.
If FCrDNS fails
Align the forward DNS name and the IP so the reverse name resolves back correctly.
If rDNS is clean
Keep it as a baseline and monitor for provider pool changes or new RBL listings.
Reverse DNS checker FAQ
Can Lens change my PTR?
No. PTR records are controlled by the IP owner or hosting provider. Lens tells you what to ask them to fix.
Is rDNS enough for deliverability?
No. It is infrastructure hygiene; reputation also depends on listings, sending behavior, and mailbox-provider signals.
Does Lens check private Gmail IP reputation?
No. Lens checks public external signals only.