Check sending IP reputation before infrastructure burns the campaign.
Paste IPv4 or IPv6 sending IPs and Lens checks public RBL exposure, PTR/rDNS, forward-confirmed rDNS, and RDAP ownership context. Then it opens the same KILL / REHAB / KEEP fix plan used by the estate scanner.
IP risk is different from domain risk
Public RBL hits
A listed sending IP can sink otherwise clean domains. Lens treats multiple or severe IP listings as a stop-sending signal.
PTR/rDNS hygiene
Missing or mismatched reverse DNS makes infrastructure look unfinished. Fix it before adding volume.
Shared pool risk
If the IP belongs to a dirty shared pool, delisting is not enough. Move to cleaner infrastructure and prove it with a re-scan.
How to act on the IP verdict
KILL
Pause sending through the IP, identify the source, and rebuild or migrate before delisting. Do not keep sending while the IP is publicly listed.
REHAB
Fix PTR/rDNS, repair forward-confirmed DNS, or clear a limited listing before warming or scaling traffic.
KEEP
Save the scan as a baseline and monitor weekly for new RBL hits, PTR drift, and provider pool changes.
IP blacklist checker FAQ
Is this the same as domain blacklist checking?
No. Domain checks look at authentication, MX, and domain-oriented DNSBL exposure. IP checks look at infrastructure reputation, PTR/rDNS, and IP RBLs.
Why do some RBL checks say unavailable?
Some lists block public resolvers or rate-limit lookups. Lens marks those as coverage gaps, not clean results. The full audit rechecks them directly.
Can I paste domains and IPs together?
Yes. The main Folderly Lens scanner accepts mixed domains and IPs in one textarea and returns one combined estate risk map.