IP blacklist lookup
Check a specific sending IP rather than assuming the website address reflects SMTP reputation.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Check a domain or public IP against DNSBL and blocklist sources, and separate confirmed listings from query errors.
No listings detected
| Identity | Role | Note |
|---|---|---|
| 203.0.113.25 | Mail exchanger | Inbound-related |
| 198.51.100.12 | Website / CDN | Informational. May not send mail |
| Unknown | Outbound SMTP IP | Not always inferable from public DNS |
Use the domain or the real outbound IP.
We check selected DNSBL sources.
Listings and errors are shown separately.
Find the cause, then follow the operator's process.
Check a specific sending IP rather than assuming the website address reflects SMTP reputation.
Use domain-focused sources for domain reputation.
Special DNSBL error codes show as unknown or provider errors, not listings.
Website, CDN, MX and sender identities are labelled separately.
Investigate abuse, compromise or complaint spikes before delisting.
Combine blocklist results with authentication, headers and list hygiene.
Blocklists are policy datasets exposed through DNS. They are not a universal spam score.
| Common assumption | What is actually true |
|---|---|
| Clean means inbox-safe | Public blocklists are one part of receiver filtering |
| Check the CDN IP | Website IP reputation may be unrelated to SMTP |
| Every 127.* answer is a listing | Some operators reserve these for errors or policy |
| Request delisting right away | Fix the cause first, or the listing will return |
Large mailbox providers use proprietary filtering beyond public lists.
A website IP and an SMTP IP serve different roles.
Some operators return these codes for errors, limits or policy.
If the cause persists, the listing is likely to return.
Blocklist status is not the same as sender reputation. Mail can still be filtered or rejected when public DNSBL checks are clean, because mailbox providers use their own signals.
Check when bounces or complaints spike.
Check new sending IPs before you warm them up.
Watch critical sending IPs on a schedule.
A tool that tests a domain or IP against selected DNSBL sources. It is a diagnostic, not a guarantee of inbox placement.
A DNS-based blocklist. Different operators publish them with different policies and purposes.
Check the identity that matches the problem. Your website, MX and outbound SMTP IPs can all differ.
No. It only means the tested sources reported no listing, and providers use many other signals.
No. The impact depends on the specific list and on how each receiver uses it.
Providers may restrict resolvers, rate-limit queries or return special codes. Errors are shown separately from listings.
Fix the root cause first, then use the operator's official removal process. Otherwise relisting is likely.
Usually not, because website and SMTP IPs serve different roles.
After incidents, infrastructure changes or delivery drops, and on a schedule for critical sending IPs.
Continue with SPF, DKIM, DMARC, DNS, header and recipient-quality checks.
Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.