Email Blacklist Check
Check whether your mail server’s IP or your domain is on a spam blocklist, why, and how to get it removed.
- Live DNS lookup
- Results in seconds
- No sign-up
- Free
-
Note:4 lists couldn’t be checked
Spamhaus DBL, SURBL, Spamhaus ZEN, NiX Spam didn’t give us a usable answer, so we can’t say either way. Each list’s own lookup page is linked in the table.
-
OK:Not listed on any blocklist we could check
github.com and its mail servers are clear on all 25 checks that answered.
github.com Domain blocklists
| Blocklist | Result | Lookup |
|---|---|---|
| Spamhaus DBL Widely used | Couldn’t check: too many queries | Look up |
| SURBL Widely used | Couldn’t check: the list didn’t answer | Look up |
| URIBL | Not listed | Look up |
52.101.40.28 MX github-com.mail.protection.outlook.com
| Blocklist | Result | Lookup |
|---|---|---|
| Spamhaus ZEN Widely used | Couldn’t check: too many queries | Look up |
| Barracuda Widely used | Not listed | Look up |
| SpamCop Widely used | Not listed | Look up |
| Mailspike | Not listed | Look up |
| PSBL | Not listed | Look up |
| NiX Spam | Couldn’t check: the list didn’t answer | Look up |
| GBUdb Truncate | Not listed | Look up |
| Backscatterer | Not listed | Look up |
52.101.60.65 MX github-com.mail.protection.outlook.com
| Blocklist | Result | Lookup |
|---|---|---|
| Spamhaus ZEN Widely used | Couldn’t check: too many queries | Look up |
| Barracuda Widely used | Not listed | Look up |
| SpamCop Widely used | Not listed | Look up |
| Mailspike | Not listed | Look up |
| PSBL | Not listed | Look up |
| NiX Spam | Couldn’t check: the list didn’t answer | Look up |
| GBUdb Truncate | Not listed | Look up |
| Backscatterer | Not listed | Look up |
52.101.40.53 MX github-com.mail.protection.outlook.com
| Blocklist | Result | Lookup |
|---|---|---|
| Spamhaus ZEN Widely used | Couldn’t check: too many queries | Look up |
| Barracuda Widely used | Not listed | Look up |
| SpamCop Widely used | Not listed | Look up |
| Mailspike | Not listed | Look up |
| PSBL | Not listed | Look up |
| NiX Spam | Couldn’t check: the list didn’t answer | Look up |
| GBUdb Truncate | Not listed | Look up |
| Backscatterer | Not listed | Look up |
52.101.194.11 MX github-com.mail.protection.outlook.com
| Blocklist | Result | Lookup |
|---|---|---|
| Spamhaus ZEN Widely used | Couldn’t check: too many queries | Look up |
| Barracuda Widely used | Not listed | Look up |
| SpamCop Widely used | Not listed | Look up |
| Mailspike | Not listed | Look up |
| PSBL | Not listed | Look up |
| NiX Spam | Couldn’t check: the list didn’t answer | Look up |
| GBUdb Truncate | Not listed | Look up |
| Backscatterer | Not listed | Look up |
Advertisement
How blocklists work
A blocklist (DNSBL) is published in DNS. To ask whether 192.0.2.25 is on Spamhaus
ZEN, a mail server looks up 25.2.0.192.zen.spamhaus.org. No answer means not
listed; an answer such as 127.0.0.2 means listed, and the number says why. Domain lists
work the same way with the domain name in front, so filters can check the links in a message as
well as the server that sent it.
Which listings matter
Spamhaus is the one to worry about: Gmail, Microsoft and most spam filters use it. Barracuda and SpamCop come next, used by many business filters. Smaller lists rarely block mail on their own, but they feed into spam scores, and a listing there is often an early sign of a problem.
Getting removed
- Find the cause first. Usually a hacked mailbox or website, a contact form sending spam, malware on a machine behind the same IP, or mail to an old or bought list. Delisting without fixing it gets you listed again, and some lists then make removal slower.
- Use the list’s own removal page. It’s linked next to each listing. Removal is free on all the lists we check; nobody legitimate charges for it.
- On shared hosting or a cloud IP? Another customer may have caused the listing. Ask your provider; they can move you to a clean address or send your mail through their relay.
Keep off them
Authenticate your mail with SPF, DKIM and DMARC, send only to people who asked for it, remove addresses that bounce, and give your sending IP a reverse DNS name that points back. The email domain health check covers the authentication side.
Frequently asked questions
What is an email blacklist?
A list of IP addresses or domains that have sent spam, published in DNS so mail servers can look them up in milliseconds. If your server’s IP or your domain is on a list a receiver uses, your mail may be rejected or sent to junk. They’re also called blocklists or DNSBLs.
Which IP addresses do you check for a domain?
The IPv4 addresses of its mail servers (MX records), up to four, or the domain’s own A record if it has no MX. The domain itself is checked against domain blocklists. To check the server you send from, enter its IP address; it’s often different from the MX servers that receive your mail.
How do I get removed from a blacklist?
Fix the cause first, or you’ll be listed again: a compromised account or server, a contact form abused to send spam, or mail to old or bought lists. Then use the list’s removal page, linked next to each listing. Some lists, like SpamCop, remove you automatically once the spam stops.
Why does a list say “couldn’t check”?
Some lists refuse lookups from busy servers or public DNS resolvers, and some only answer registered users. When a list gives no usable answer we say so rather than call you clean. Its own lookup page, linked in the table, will tell you.
My IP is on the Spamhaus PBL. Is that bad?
Not in itself. The PBL lists home and dynamic addresses that shouldn’t send mail straight to the internet. It only matters if your mail server sends from that address; if so, use a static IP meant for mail or send through your provider’s relay.
Did this tool do what you needed?
Related tools
All toolsEmail Domain Health Check
SPF, DKIM, DMARC and MX checked together, with a score and a list of fixes.
Reverse DNS Lookup
Find the hostname behind an IP address (PTR record) and whether it points back.
SPF Record Checker
Validate an SPF record, follow every include and count DNS lookups against the limit of 10.