The short answer: To check an email blacklist, query your sending IP addresses and domain against DNS-based blocklists (DNSBLs). A free multi-list tool does this in seconds: enter your domain, then look at which zones return a listing. If you are listed, fix the cause first, then follow that blocklist's own removal process, and re-check after it takes effect.
DNSBLs Versus Reputation Systems
People use "blacklist" for two quite different things, and the difference decides what you can fix.
DNSBLs (DNS blocklists) are public lists, published through DNS, of IP addresses or domains. Anyone can query them, and many mail servers do so during delivery. They are binary: listed or not. Examples include Spamhaus ZEN, Barracuda's BRBL and SpamCop.
Reputation systems are private scores that large providers keep about you. Gmail, Microsoft and Yahoo do not publish a list you can query. They weigh complaints, bounces, authentication, engagement and history, and they decide placement themselves. You see them only indirectly, through Google Postmaster Tools or Microsoft SNDS, or through rejection messages.
| DNSBL | Provider reputation | |
|---|---|---|
| Public to query | Yes | No |
| Result | Listed or not listed | Placement decision, sometimes a dashboard |
| Fix | Fix cause, request removal | Fix cause, then build positive history over time |
| Request removal | Usually yes | Usually no formal delisting, though Microsoft has a support route for blocked IPs |
| Checked by this tool | Yes | No |
So a clean DNSBL result does not mean Gmail trusts you. It means that one common cause of rejection is ruled out.
How a DNSBL Lookup Works
A blocklist is queried with an ordinary DNS request. To check IP 198.51.100.24 against Spamhaus ZEN, a mail server reverses the octets and appends the zone:
24.100.51.198.zen.spamhaus.org
If the name does not exist, the IP is not listed. If it returns an A record in the 127.x.x.x range, it is listed, and the specific address tells you why. For example, ZEN uses 127.0.0.2 and 127.0.0.3 for its SBL entries, 127.0.0.4 to 127.0.0.7 for exploited-host data (XBL) and 127.0.0.10 or 127.0.0.11 for the Policy Block List (PBL). Domain lists such as Spamhaus DBL work the same way but look up the domain name directly.
Two special Spamhaus answers, 127.255.255.254 and 127.255.255.255, do not mean you are listed. They indicate the query was refused, typically because it came through a public DNS resolver or exceeded a rate limit. Tools that treat them as listings produce false positives.
What the Blacklist Checker Actually Queries
The blacklist checker takes a domain and does the following:
- Resolves the domain's IPv4 address records.
- Resolves the domain's MX records and looks up the IPv4 addresses of the first three mail hosts.
- Checks every resulting IP against 11 IP-based zones, and the domain name against the Spamhaus domain list.
- Groups the results by zone: if any IP is listed on a zone, that zone shows as listed.
The 12 zones and their severity labels in the tool:
| Zone | Name in results | Type | Severity |
|---|---|---|---|
| zen.spamhaus.org | Spamhaus ZEN | IP | Critical |
| dbl.spamhaus.org | Spamhaus DBL | Domain | Critical |
| b.barracudacentral.org | Barracuda | IP | High |
| spam.sorbs.net | SORBS SPAM | IP | High |
| bl.spamcop.net | SpamCop | IP | High |
| dnsbl-1.uceprotect.net | UCEPROTECT L1 | IP | Medium |
| blacklist.lashback.com | LashBack | IP | Medium |
| ivmsip.invaluement.com | Invaluement | IP | Medium |
| spam.abuse.ch | Abuse.ch | IP | Medium |
| dnsbl.dronebl.org | DroneBL | IP | Medium |
| bl.mailspike.net | Mailspike BL | IP | Low |
| truncate.gbudb.net | Truncate | IP | Low |
Reading the verdict
- Pass. No zone returned a genuine listing.
- Warn. At least one listing, but none on a critical-severity zone.
- Fail. At least one critical zone, which means Spamhaus ZEN or DBL, lists you.
Each listing also shows the return code, such as 127.0.0.2, which you can match against the blocklist operator's documentation.
Example: interpreting a result
Suppose the checker returns this for yourdomain.com:
IPs checked: 203.0.113.10 (domain A record), 198.51.100.24 (MX host)
Verdict: warn
Listed: SpamCop (127.0.0.2)
Not listed: the other 11 zones
Reading it step by step: the verdict is warn because SpamCop carries high severity but not critical. The listing came from one of the two IPs, and the result does not tell you which, so check each IP on the operator's own lookup page. If 198.51.100.24 is your mail server, search its logs for the period before the listing. If 203.0.113.10 is a shared web host, the listing may have nothing to do with your mail at all. Next, decide whether the listing matches a real event, such as a campaign to an old list, before you request anything.
Limits you should know about
- It checks your domain's own IPs and inbound mail hosts. If you send through a third party such as Google Workspace, Microsoft 365 or an email platform, your outgoing IP is probably not among them. Find the real sending IP in a message's
Receivedheaders (the email header analyzer helps) and check that. - A website on shared hosting or a CDN may share an IP with other sites, so a listing may relate to the host and not your mail.
- IPv4 only. IPv6 sending addresses are not looked up.
- A failed or timed-out lookup is shown as not listed. A clean result is strong evidence, not proof.
- It does not query every list. Spamhaus ZEN covers SBL, XBL and PBL data, but other lists such as SURBL are not in the 12.
- Zone availability changes. Blocklists are run by independent organisations that merge, change policy or shut down. Treat each zone's weight as of the time you read it.
Why You Get Listed
Removal without fixing the cause usually fails, so identify the trigger:
- Compromised mailbox or server sending spam. The most serious cause, and one that often shows as a sudden surge in outbound mail.
- Spam trap hits from old, scraped or purchased lists.
- High complaint rates reported to feedback or abuse systems.
- Sending from a dynamic or residential IP range. Spamhaus PBL lists ranges that are not supposed to send mail directly. This is policy, not accusation, and you can usually request removal for a static business IP you control.
- Neighbour effects on shared IPs, or on ranges that lists such as UCEPROTECT treat in aggregate.
- Newly registered domains with spam-like behaviour, which domain lists tend to flag fast.
Authentication does not directly cause listings, but weak authentication makes spoofed spam in your name more likely. See SPF, DKIM and DMARC explained.
How Delisting Works
Every operator has its own policy, and these change. Always start from the operator's own lookup page, which shows the listing reason and the removal route.
| List | Typical approach |
|---|---|
| Spamhaus | Look up the IP or domain on Spamhaus's check page. It shows which list applies and links to the relevant removal route. SBL and DBL listings generally need the underlying issue resolved. PBL entries for static IPs can usually be removed by the IP's rightful user. |
| Barracuda (BRBL) | Barracuda provides a lookup and a removal request form on its Central site. It asks for your contact details and the IP. |
| SpamCop | Listings are driven by user reports and are designed to expire on their own once the reports stop. |
| UCEPROTECT | Levels differ in scope. Level 1 concerns individual IPs, while higher levels cover wider ranges, so you may be listed because of neighbours. The operator also offers paid expedited removal; whether to use it is your call. |
| Others | Check each operator's website for its criteria. Some are automated and expire without action. |
Microsoft handles blocked IPs for Outlook.com and Microsoft 365 recipients through its own sender support process, not a public DNSBL.
The sequence
- Stop the cause. Disable or reset compromised accounts, enforce MFA, remove the bad list segment, or fix the misconfigured server.
- Collect evidence of what you did, because some operators ask.
- Submit removal only to lists that offer it, and be factual and brief.
- Re-check with the checker after the operator says it has acted. DNS caching means changes can take a little while to be visible.
- Monitor for several weeks. A repeat listing usually means the cause is still active.
Do not keep sending bulk mail while listed, and avoid hopping to new IPs to dodge the listing, which tends to damage reputation further.
After You Are Clear
- Check the email security score so SPF, DKIM and DMARC are in order.
- Move toward DMARC enforcement with the DMARC policy guide, so others cannot send in your name.
- Warm up any new IP or domain with the email domain warm-up guide.
- If mail still lands in spam with no listings, go to why are my emails going to spam.
- Run through the deliverability checklist to find what is left.
Frequently Asked Questions
Why does my domain look blacklisted when I only use Google Workspace or Microsoft 365?
The checker looks at the IPs for your domain and its MX hosts, which belong to your provider or hosting. A listing there may relate to a shared address, not your own sending. Check the actual outgoing IP in a message header before taking action.
How long does it take to get removed from a blacklist?
It depends on the operator. Some listings expire automatically, some need a manual request, and some are reviewed by people. There is no universal timeline, so check the operator's own guidance.
Is being on one low-severity blacklist a problem?
Often not, because few receivers use every list. Still, find out why you were listed, since the cause may also affect your reputation elsewhere.
Can I be blacklisted without sending spam?
Yes. Compromised accounts, shared IP neighbours, dynamic IP ranges and recycled addresses can all cause listings without you deliberately sending anything abusive.
Does blacklist removal guarantee my email reaches the inbox?
No. It removes one block. Providers like Gmail also use their own reputation scoring, so inbox placement depends on authentication, engagement and consistency as well.
Next Step
Run the blacklist checker or the free email audit. If you are listed on several lists or cannot find the cause, our email security setup service can help diagnose and fix it.