Is your domain or IP on a blocklist?
Eight public blocklists queried in one go, with the reason for each listing and the link to request removal.
How it works
- Enter a domain or an IP address — you can also paste a URL or an email address, and we'll extract the domain from it.
- We query eight public blocklists in parallel — three domain lists and five IP lists. For a domain we also resolve its address and its mail servers (MX), so the IPs that actually send your mail get checked too.
- You get the verdict list by list — listed (with the reason and the removal link), clean, or undetermined when a list didn't answer.
Use cases
- Your emails land in spam or bounce back — a listing on Spamhaus or SpamCop is the first cause to rule out before suspecting the content of your messages.
- You've just changed server or host — a freshly assigned IP address sometimes carries the reputation of whoever had it before you.
- A mailbox on your domain was compromised — once the password is changed, you still need to check whether the domain or IP got listed in the meantime, and ask for removal.
- Before a campaign or an important send — checking beforehand costs a few seconds; repairing afterwards costs weeks of reputation.
- You've taken over a second-hand domain — a domain once used for spam stays on the domain lists long after it changes hands.
What this tool doesn't do
- It queries eight public lists, not the internal lists of the large providers. Gmail, Outlook and Yahoo keep their own reputation scores, invisible from the outside: being clean everywhere here doesn't guarantee inbox placement.
- It doesn't request removal for you. Every list has its own procedure; we give the direct link, the request stays yours — and it fails as long as the cause isn't fixed.
- It doesn't monitor over time: this is a check at a single point in time, with no alert if a listing appears later.
- The lists we use only index IPv4; an IPv6 address is reported as not covered rather than falsely clean.
- An "undetermined" verdict is not a "clean" one. When a list doesn't answer, we say so — it's the only honest verdict.
Frequently asked questions
What is a DNS blocklist (DNSBL)? +
It's a database, queried over DNS, listing IP addresses or domains associated with abusive sending. Mail servers check it before accepting a message: if your sending address is on it, your emails land in spam or are rejected outright.
Which lists are queried? +
For an IP address: Spamhaus ZEN, SpamCop, PSBL, Mailspike and SpamRATS. For a domain: Spamhaus DBL, SURBL and URIBL. All of them are actually consulted by mail operators, free to query, and free and documented to get removed from. We deliberately leave out lists whose removal is paid for.
What happens if I enter a domain rather than an IP? +
We check the domain against the domain lists, then resolve its address and its mail servers (MX) to check those IP addresses against the IP lists. That's often where the problem is: a spotless domain can still send from a server whose IP is listed.
What does "undetermined" mean? +
That the list didn't answer: timeout, quota reached, or query refused. We never turn that into "clean". A silent blocklist proves nothing, and letting you believe otherwise would be the most useful kind of lie — therefore the worst.
I'm listed: how do I get removed? +
Every list has its own procedure, and the result shows the direct link to the matching removal page. Before you ask, fix the cause: a compromised mailbox, an exploited contact form, an open relay, or bulk sending without consent. A removal obtained without a fix is followed by another listing.
Are IPv6 addresses covered? +
No, and we say so plainly rather than showing a false "clean". The lists we use only index IPv4. If your server sends over IPv6, check the matching IPv4 address, which is almost always the one being judged.
Is my check recorded? +
The result is kept in a technical cache for a few minutes to avoid querying the lists again needlessly, then it's gone. We build no search history, and no data is passed to any third party beyond the DNS queries the check itself requires.