Email Blacklists: Check Your Domain or IP and Get Removed

To get off an email blacklist, first check which list has your IP address or domain, then find and fix whatever caused the listing, and only then request removal on that list's own website. Most major lists, including Spamhaus, Barracuda and SpamCop, delist for free, and some expire listings on their own once the problem stops. Requesting removal before fixing the cause usually gets you listed again within days.

This guide is for business owners and server admins seeing bounces that mention a blocklist, or emails that suddenly stopped reaching customers. It covers the difference between domain and IP listings, the main lists and how each one handles removal, and the reverse DNS setup your own mail server needs. If your problem is a browser warning on your website rather than email, see the Google dangerous site warning guide instead.

#Domain reputation vs IP reputation

There are two kinds of listing, and the fix depends on which one you have.

If you send through Google Workspace, Microsoft 365 or a service like Amazon SES or Brevo on shared IPs, an IP listing is the provider's problem and they handle it. Domain listings follow you whatever service you use, so they are always yours to fix.

#The major blacklists and how removal works

Thousands of lists exist, but only a few are widely used by mail servers. These are the ones worth acting on.

A few points from the lists' own pages are worth knowing before you act:

• Spamhaus handles DBL, PBL and CSS removals through one tool, its IP and Domain Reputation Checker. Removal is free. For CSS it warns that an IP will be listed again immediately if the problem continues.
• Barracuda asks for the IP, an email address and a phone number, and ignores requests without valid information or repeated requests.
• SpamCop asks admins not to request early delisting. After the listing expires, removal can take up to 4 hours to reach everyone using the list.
• UCEPROTECT Level 1 listings expire automatically, so paying for express removal is optional. Levels 2 and 3 list whole provider ranges, which only your hosting provider can fix.

#Step 1: check your IP and domain

1. Find your sending IP. Open the headers of a message you sent (in Gmail: More, then Show original) and look at the first Received line added by the receiving server. For your own server, it is the server's public IP.
2. Read the bounce. Rejection messages often name the list and include a lookup link. That is the fastest clue.
3. Check Spamhaus. Enter the IP and your domain at check.spamhaus.org. Spamhaus advises checking related domains too, since domain and IP reputations are linked.
4. Check Barracuda at its lookup page on barracudacentral.org, and SpamCop at spamcop.net.
5. Use a multi-list checker to scan many lists at once, then ignore obscure lists that few mail servers use. Focus on the ones in the table above.

#Step 2: find and fix the cause

Removal without a fix is wasted effort. Look for these, roughly in order of how often they cause listings:

• A hacked website sending spam through its contact form or a planted script. Check the server's mail queue and logs. If the site is compromised, clean it first; the hacked WordPress cleanup guide covers the signs.
• A stolen mailbox password used to send spam through your real account. Reset passwords and turn on two-factor sign-in.
• An infected office computer, which is what XBL listings usually mean. Scan every device behind that IP.
• Website forms with no spam protection, used to send messages to strangers.
• Bought or very old lists, which hit spam traps and drive complaints.
• Sending direct from a home or dynamic IP, which PBL lists by design. Send through your email provider or an SMTP service instead.
• A misconfigured server with wrong forward DNS, reverse DNS or HELO name. Spamhaus says SMTP servers should be configured with correct forward and reverse DNS and HELO/EHLO values.

#Step 3: request removal

Once the cause is fixed, go to each list's own site and follow its process. Request removal once per list. Explain briefly what happened and what you changed. Never pay a third party who promises delisting; the main lists remove for free, and the only paid option among them, UCEPROTECT's express removal, is optional because Level 1 listings expire on their own.

After removal, watch your bounces and recheck the lists daily for a week. If you are relisted, the cause is still active.

#Reverse DNS (PTR) and FCrDNS for your own server

If you run your own mail server on a VPS, reverse DNS is not optional. Google's sender guidelines require every sender to have valid forward and reverse DNS: the sending IP needs a PTR record that resolves to a hostname, and that hostname needs an A or AAAA record that resolves back to the same IP. This round trip is called forward-confirmed reverse DNS, or FCrDNS. Yahoo asks for the same.

The PTR record is set in your VPS provider's control panel or by its support team, not at your domain registrar, because the provider owns the IP. Avoid generic PTR names that look like home connections. Running your own mail server also means patching, monitoring queues and watching lists, which is part of VPS and cloud server management.

#When to get help

You can handle a single SpamCop or Barracuda listing yourself if you know what caused it. Get help when you cannot find the cause, when you are relisted after removal, when a domain is on the Spamhaus DBL, when your own server has no PTR record, or when invoices and order emails are bouncing right now. A listing that keeps coming back usually means a compromised site or account that is still sending.

My email deliverability service covers the cause, the cleanup, the removal requests and the monitoring afterwards. For the wider picture of why mail lands in spam, read why your emails go to spam.