If your email suddenly stops landing, a blacklist listing is one of the first things to rule out. A blacklist, more precisely a DNSBL (DNS-based blocklist), is a live list of sending IP addresses or domains that receiving mail servers query in real time to decide whether to accept, reject, or spam-folder your message. To check if you are listed, look up your sending IP (not just your domain) against the major blocklists, confirm the listing is on a list that receivers actually use, then fix the root cause before you request removal.
The trap most people fall into is delisting without fixing why they were listed. You get removed, the abusive traffic or broken authentication continues, and you land right back on the list within days. Get the cause right first and the removal sticks.
Reads public DNS only. Nothing is stored unless you save the domain to an account.
Domain blacklist vs IP blacklist: know what you are checking
Most DNSBLs list IP addresses, not domains. When a receiver evaluates your message, it takes the IP that connected to it and does a reversed DNS query against each blocklist it trusts. So the primary thing to check is the public IP your mail actually leaves from.
Find that IP first. If you send through Google Workspace, Microsoft 365, Amazon SES, SendGrid, Mailchimp, or any other provider, the sending IP belongs to them, not you, and you usually cannot delist a shared provider IP yourself. If you run your own mail server on a VPS or on-premise box, the IP is yours and you are responsible for it. Check the Received: headers of a recent outbound message, or your provider's documentation, to confirm which IP receivers see.
There are also domain and URL blocklists (Spamhaus DBL, SURBL, URIBL) that list the domains appearing in message bodies and envelope, independent of the sending IP. These matter if your domain name shows up in spam that someone else sent, or if a page on your domain was compromised. Check both dimensions: the IP you send from and the domain in your links.
Which DNSBLs actually move the needle
There are hundreds of blocklists. Fewer than a dozen have enough adoption to change whether your mail is delivered. Spend your energy here and ignore the rest.
The lists that matter
- Spamhaus (SBL, XBL, PBL, DBL, ZEN). The single most important operator. ZEN is the combined zone most receivers query. A Spamhaus listing is a real deliverability problem and you should treat it as urgent.
- Barracuda (BRBL). Widely used by Barracuda appliances in front of corporate mail. A listing here hits B2B delivery hard.
- SpamCop (SCBL). Complaint-driven and fast to expire, but heavily consumed. Listings usually auto-clear within 24 to 48 hours once the trigger stops.
- Microsoft. Not a public DNSBL, but Outlook, Hotmail, and Live use their own internal reputation and SNDS/JMRP data. Being blocked here means using Microsoft's Sender Support form, not a delisting webpage.
- Proofpoint and Cloudmark. Vendor reputation systems in front of large enterprises. Harder to inspect, but if enterprise recipients bounce with their signatures, this is the cause.
The lists to check but weigh carefully
- UCEPROTECT (Level 1 is IP-specific; Levels 2 and 3 list entire ranges and ASNs). Level 1 can be legitimate. Levels 2 and 3 punish you for a neighbor's behavior on shared hosting and are widely regarded as aggressive. Many receivers ignore them. Do not panic over an L2 or L3 listing alone.
- SORBS. Historically noisy and slow to delist. Its influence has faded and it wound down operations, so a SORBS-only listing rarely explains a delivery problem in 2026.
Vanity lists to ignore
Dozens of small "RBLs" exist that almost no mail server queries. If a listing appears only on an obscure list you have never heard of and nowhere on Spamhaus or Barracuda, it is not causing your delivery issue. Chasing every one of them wastes time. Judge a listing by who consumes it, not by the fact that it exists.
Run the root-cause checklist before you delist
Delisting is the last step, not the first. Work through this before you submit any removal request, or you will be back on the list within a week.
1. Confirm SPF, DKIM, and DMARC pass
Broken authentication is a leading reason mail gets flagged as spam-like, which drives complaints and listings. Run your domain through the checker above and verify all three pass and align. If they do not, fix them first: set up SPF, set up DKIM, and set up DMARC. A published, aligned setup looks like this on the DNS side:
example.com. TXT "v=spf1 include:_spf.google.com -all"
_dmarc.example.com. TXT "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
2. Check for compromise
A listing that appears out of nowhere often means an account or server was compromised and is sending spam. Look for a spike in outbound volume, unfamiliar recipients in your logs, or a large queue of bounces you did not create. Rotate credentials, patch the server, and close any open relay before anything else. Review your business email compromise checklist if you suspect an account takeover.
3. Clean your sending practices
Spamhaus and complaint lists respond to real signals: sending to purchased or scraped lists, ignoring unsubscribes, hitting spam traps, or a sudden volume spike from a cold IP. Remove hard bounces, honor opt-outs immediately, and if you are on a new IP, warm up the domain gradually instead of blasting full volume on day one.
4. Fix reverse DNS and HELO
Every sending IP should have a matching PTR record and a consistent HELO/EHLO name. A missing or generic PTR (like the default hostname your VPS provider assigns) is a listing trigger on several blocklists and a spam signal everywhere. Set the PTR to a hostname you control that forward-resolves back to the same IP.
How to request delisting, per operator
Once the cause is fixed, removal is usually straightforward. Each operator runs its own process.
- Spamhaus: use the Spamhaus Blocklist Removal Center, look up the IP, and follow the per-listing instructions. XBL and CSS listings often clear automatically once the bad traffic stops. PBL delisting is self-service for IPs that should be allowed to send.
- Barracuda: submit the IP through Barracuda Central's removal request form.
- SpamCop: usually no action needed. Listings expire automatically 24 to 48 hours after the last reported spam. If it persists, the traffic has not actually stopped.
- UCEPROTECT: Level 1 offers an express (paid) removal, but free removal happens automatically after seven days with no new activity. For Level 2 and 3, you generally cannot remove a range listing yourself, which is one more reason not to over-index on them.
- Microsoft: use the Microsoft Sender Support / delisting form and, for ongoing sending, enroll the IP in SNDS and JMRP to see complaint data.
- SORBS and others: use the operator's own removal page linked from the listing detail.
Give DNS and reputation systems time to propagate after removal. A delisting can take a few hours to reflect at every receiver.
Why listings come back, and how to make removal stick
A blacklist listing is a symptom. The list is telling you that receivers saw behavior they associate with spam: bad authentication, a compromised sender, dirty lists, or a bad-neighborhood IP. If you only remove the listing, the underlying signal is still there and the automated systems relist you.
Sticking the landing means the authentication is clean and aligned, the compromise is closed, the list hygiene is real, and the IP has a proper PTR. This is also exactly what the Google and Yahoo sender requirements demand, so fixing it once solves both problems at the same time. If mail is landing in spam without an actual blocklist entry, the cause is usually reputation and authentication rather than a listing, and why emails go to spam walks through those signals.
Frequently asked questions
How do I find the IP address to check on a blacklist?
Open a message you recently sent and read the Received: headers from the bottom up. The first public IP that handled your outbound mail is the one receivers see and the one you check against DNSBLs. If you send through a provider like Google Workspace or SES, that IP belongs to them and you cannot delist it yourself. Contact the provider instead.
Does being on a blacklist always mean my email is blocked?
No. It depends on which list and which receivers query it. A Spamhaus or Barracuda listing has real impact because major mail systems trust those lists. A listing on an obscure vanity RBL that almost nobody queries has close to zero effect. Judge a listing by its adoption, not by the fact that it exists.
How long does delisting take?
It varies by operator. SpamCop and UCEPROTECT Level 1 often clear automatically within one to seven days once the triggering activity stops. Spamhaus self-service and Barracuda removals typically take effect within hours after you submit and the cause is resolved. Propagation across all receivers can add a few more hours.
Can bad SPF or DKIM get me blacklisted?
Not directly by syntax alone, but broken or unaligned authentication makes your mail look spoofed and spam-like, which drives spam-folder placement and recipient complaints. Those complaints are exactly what feed complaint-driven blocklists like SpamCop. Passing and aligned SPF, DKIM, and DMARC removes that entire category of trigger, which is why it is step one of the checklist.