Blacklist Lookup
Check an IP or domain against public DNS blocklists
- 100% Free
- Files stay private
- Works in your browser
IP or domain
Enter an IPv4 address, or a domain we'll resolve to its IP, to check it against public DNS blocklists.
Queried live from our server across ~24 public DNSBLs. Some zones rate-limit public resolvers, so an occasional gap or timeout is normal. A listing on one or two minor lists isn't always cause for concern.
How it works
Enter IP or domain
Type an IPv4 address or a domain into the IP address or domain field; a domain is resolved to its IP first.
Press Check blacklists
Our server checks the IP against about 24 public DNS blocklists and shows which ones list it.
Read the verdict
You get a clean or listed verdict, plus a Zone breakdown showing the result from each blocklist.
Enter an IP address or a domain and this tool checks it against roughly two dozen public DNS blocklists at once, the same kind of lists mail servers consult before deciding whether to accept a message. In a few seconds you get a plain verdict: clean, or listed on some number of blocklists, along with the exact zones that flagged it.
What Is Blacklist Lookup?
Blacklist Lookup is a free tool that runs DNSBL (DNS-based blocklist) queries against about 24 well-known public zones: Spamhaus ZEN, SpamCop, Barracuda, SORBS, UCEPROTECT, SpamRATS, and others. DNSBLs track IP addresses, so when you enter an IP, our server reverses its four octets and asks each blocklist a DNS question in the form reversed-ip.zone. If that name resolves, the IP is listed and the returned 127.0.0.x code is the reason the list assigns; if nothing resolves, it's clean there.
Enter a domain instead and the tool first resolves its A record to an IPv4 address, then checks that. The lookups run in parallel through the Cloudflare (1.1.1.1) and Google (8.8.8.8) resolvers, and the result tells you how many zones were checked, how many listed the IP, and whether it came back completely clean.
Who Benefits from This Tool
- Email administrators: confirm a sending IP isn't blocklisted before a campaign, and explain why messages bounce or land in spam.
- System administrators: check a server's public IP after a migration in case you inherited a bad reputation.
- Deliverability specialists: pinpoint which specific list is hurting inbox placement so you can work on delisting.
- Security analysts: test a suspicious IP against abuse lists like DroneBL and SpamRATS to see if it's a known offender.
- Developers: verify the IP behind a transactional email service is trusted before wiring it into production.
- VPS and hosting buyers: vet an assigned address before committing, in case a previous tenant got it listed.
Key Features
- Two dozen lists in one query: around 24 public DNSBL zones checked in parallel, so you skip visiting each list by hand.
- Clear verdict: a single green "not listed" or red "listed on N blocklists" answers the question at a glance.
- Per-zone breakdown: every blocklist is shown with a listed or clean badge, and the listed ones are highlighted.
- IP or domain input: paste an IPv4 address directly, or a domain and let the tool resolve its A record first.
- Listing reason capture: when a zone lists the IP, its raw 127.0.0.x response is recorded, which many lists use to encode why.
- No setup: it runs from the page through public resolvers, with no account, API key, or install.
How to Use
- Enter an IPv4 address (for example, 8.8.8.8) or a domain name.
- Run the check and wait a few seconds while the zones are queried.
- Read the main verdict. Green means clean, red means listed on a specific number of lists.
- Scan the stat pills for the count of zones checked, listed, and clean.
- Review the per-zone list and note which blocklists flagged the IP.
- If you're listed, open that blocklist's own site for the reason and its delisting process.
Common Use Cases
- Diagnosing why outbound email keeps bouncing or getting filtered to spam.
- Vetting a freshly provisioned server or VPS IP before you send anything from it.
- Checking a shared-hosting IP where a noisy neighbor may have caused a listing.
- Auditing an IP after cleaning up a compromised machine to confirm abuse listings cleared.
- Verifying that a delisting request actually took effect a day or two later.
Tips and Best Practices
- Check the actual sending IP from your mail server's headers, not just your website's domain. They're often different machines.
- Weigh listings by source. A hit on Spamhaus ZEN or Barracuda affects real delivery far more than a range-based list like UCEPROTECT level 2 or 3.
- After requesting delisting, wait and re-run; DNS caching means a removal can take hours to show everywhere.
- For a domain behind a CDN, remember the tool sees the resolved A record. That may be the CDN's IP, not your mail server's.
- A clean result is a good sign but not a full audit; SPF, DKIM, and DMARC still matter for inbox placement.
Limitations and Notes
This tool queries IP-based DNSBLs. It is not a domain-reputation service, a URIBL check, or a Google Safe Browsing lookup, so a clean verdict means the IP isn't on these mail blocklists, not that a domain is malware-free. Public DNSBLs sometimes rate-limit queries from shared resolvers, so a zone can occasionally time out and report clean when it would otherwise list; if a result looks off, run the check again. Private and loopback addresses are rejected. Being listed doesn't always mean you sent spam. Dynamic ranges and shared hosts are sometimes blanket-listed for a neighbor's behavior. Finally, this tool reports status only; it cannot remove you from a list. Delisting is handled by each blocklist through its own site, and you'll usually need to fix the underlying cause first.
FAQs
DNS blocklists track IP addresses, not domain names. When you enter a domain, the tool resolves its A record to an IPv4 address and checks that. Entering the IP directly skips that step and checks exactly the address you specify.
Each blocklist runs its own delisting process on its own website, so start with the zone that flagged you. You'll usually need to fix the root cause first (a compromised account, an open relay, or spam complaints), then submit a removal request. Some lists delist automatically once the activity stops.
Public DNSBLs often rate-limit lookups from shared resolvers like the ones this tool uses, and a query that hits that limit or times out is reported as clean. That's why an occasional gap is normal. If a specific result matters, run the check again a few moments later.
It depends heavily on which list. Spamhaus ZEN, Barracuda, and SpamCop are consulted by a large share of mail servers, so a listing there can noticeably hurt delivery. Others, such as UCEPROTECT levels 2 and 3, list entire IP ranges and are used far less strictly, so their impact is usually smaller.
Around 24 public DNSBL zones, including Spamhaus ZEN, SpamCop, Barracuda Central, SORBS, the UCEPROTECT levels, SpamRATS, and DroneBL, plus several regional and abuse-focused lists. The full set appears in the per-zone results after you run a check.
The check works with IPv4 addresses and with domains that have an A record. If you enter a domain, the tool uses its resolved IPv4 address. For a host that is IPv6-only, there's no IPv4 address for these lists to check against.