Have you been blocked?
All blocklists are researched and managed by The Spamhaus Project.
Simply click on the link below, which will take you to the Project’s IP and Domain Reputation Checker. From here you will be able to enter your IP or Domain and begin your request for removal.
Please note that the Project’s IP and Domain Reputation Checker is the only place where removals are handled.
IT and security teams consistently face multiple business challenges. Discover how our solutions can help overcome some of those issues.
From processing issues, to email-borne threats our blocklists easily integrate with your current email set-up to improve anti-spam & anti-virus email filtering.
Employ our threat intelligence to increase visibility across security events, reveal potential weaknesses in your network, and threats to your brand.
Stay on top of the latest threats and proactively combat botnet infections, and other forms of abuse, with our solutions.
From clicking on phishing emails to visiting malware dropper sites, our threat intelligence provides automatic protection for your users.
Our products provide additional layers of security for networks and email. They also present security teams with additional insight into malicious behavior.
Border Gateway Protocol (BGP)
Block the worst of the worst at your network edge, taking advantage of your existing BGP-capable routers. Configuration only takes minutes.
Data Query Service (DQS)
Benefit from industry-leading real time blocklists. These DNSBLs easily plug into your existing email infrastructure to block spam and other email threats.
A powerful research tool to investigate relationships between internet infrastructures. Quickly pivot to new areas of concern to rapidly investigate potential threats.
Immediately block connections to dangerous sites, including phishing and malware dropper websites. A ‘set and forget’ solution.
Spamhaus Intelligence API
Threat intelligence data in API format to enable users to easily integrate metadata relating to threats with their own applications, programs, and products.
A wide range of datasets, providing multiple layers of protection. They can be plugged directly into your existing hardware, making them an affordable choice.
Border Gateway Protocol (BGP) Feeds
Do Not Route Or Peer (DROP) and Botnet Controller List (BCL) datafeeds can peer with your existing BGP-capable router.
Domain (DBL), Zero Reputation (ZRD) and Hash blocklists (HBL) enable you to block content in emails, filtering out a higher rate of email-borne threats.
Data for Investigation
Passive DNS and extended datasets give you additional information on internet resources. They provide deeper insights into incidents and possible threats.
DNS Firewall Threat Feeds
A wide range of feeds to apply to your DNS recursive server. Choose the right level of protection for your organization.
Spam (SBL), Policy (PBL), Exploits (XBL) and Auth (AuthBL) blocklists allow you to filter email from IPs associated with spam, botnets, and other threats.
Find out more about us.
Learn more about Spamhaus; who we are, and what we do.
Find out who we work with and how you can become a Spamhaus Partner.
Discover a wide range of blog posts, case studies and reports.
Commonly asked questions about Spamhaus products and processes.
The Blocklist Tester
A tool to help you check if your servers are correctly configured to use Spamhaus DNSBLs.
Help for Spamhaus Public Mirror users
Using the Project’s Public Mirrors and suddenly experiencing email issues? This page may be able to help.
In depth information about the technical details and implementation of our products.
Posted by Alex Grosjean on 29 Oct 2021
In celebration of Ray Tomlinson sending the first-ever networked email 50 years ago today - and introducing the '@' symbol convention - one Spamhaus Project researcher looks back into the archives to when spam fighting was 100% manual. Alex shares when they blocked the whole of Italy, and unbelievably, nobody wanted to do anything to fix it! Not until one government official complained he couldn’t email his mistress…
No kidding, there I was, with my finger on the button to block the domain “interbusiness.it“, which at the time – 2001 – was used by Telecom Italia for ALL business customers. The Italian domain was generating a significant portion of the millions of daily “This Is Spam” complaints from the user base of 34 million AOL had then, and it was getting completely out of hand. We had a mandate to reduce user-generated complaints by 95% by the end of that year, so something had to be done immediately.
The spam was originating from IPs that used the rDNS “interbusiness.it“. I had spent a couple of months trying to contact someone in charge of this domain, with no luck at all. I wrote emails. I made phone calls. Occasionally these were answered, but they always got transferred to a line that then rang out. I could not get anyone to pay attention and the spam tide was rising, so I asked management if I could take the nuclear option, and they said “yes.”
I took a deep breath and pulled the trigger, expecting an immediate explosion…but to my surprise, I was met with thunderous silence. I had anticipated a frantic email or a panicked phone call making its way to me the next day, but that didn’t happen. These were an entire nation’s business customers, right? Surely this would cause some problems? Apparently not! A month passed, during which my mother called me from Italy and asked why she could not email her Italian mother’s AOL account. At that point, I admitted that I had essentially blocked Italy from sending email to AOL, and suggested she call Nonna instead.
I waited some more. Another three weeks went by, and finally, my phone rang. On the other end of the line was a very agitated young man from Telecom Italia who told me that the mayor of his city had called him. The mayor had demanded he drop everything and fix the issue immediately, because the mayor needed to email his mistress – seriously!
AOL had recently developed a feedback mechanism by which they could – after mutual agreement – send a copy of a user-generated spam complaint back to the originating network. This would allow their abuse desks to locate and terminate the source of the spam. So when this guy called, I explained the problem and offered to set up a feedback loop for him.
He said there was no way he could make that work, but called the following day again to plead his case. We went around like this for a few days. Exasperated, I finally told him that I was coming to Italy to visit my grandmother the next week and could drop by his office in Rome to discuss it in person if he liked. He was horrified and declined.
I waited some more. Eventually, they caved, of course, and we set up the feedback loop. Over the next few years, we developed an excellent working relationship, and their spam problem declined remarkably. To this day, my mom calls me when she has problems sending email and asks me if I blocked whatever random country. No, Mom, not anymore. The machines do that for us now!
These moments to come together and share stories of times gone by are rare – never more so than now. So, to celebrate sending email over a network being 50 years old, join the community in sharing your most interesting email stories and connect using the hashtags #QWERTYUIOP and #50yrsofemail
This API provides access to metadata relating to IP addresses exhibiting compromised behavior, including malware, worm and trojan infections, and SMTP-specific traffic emitting spam.
The breadth of data available via an easily consumable API provides security developers with scores of opportunities.
Spamhaus’ Data Query Service (DQS) is an affordable and effective solution to protect your email infrastructure and users.
Using your existing email protection solution, you will be able to block spam and other related threats including malware, ransomware, and phishing emails.
The service has never failed and utilizes the longest established DNSBLs in the industry.
30 November 2021
I write this article for all of you out there who aren't deeply embedded in this industry because the people I work with are remarkable. The world should know what they are doing to quietly protect all those who say “Spamwho?” be that your grandma or the network nerd at work.
19 November 2021
When a new top-level domain (TLD) is starting out, we understand that it needs to find its way to being commercially viable. But registries need to walk a fine line between profit and managing abuse on their TLD.
19 October 2021
Here's a story of doorbells, specific software development kits (SDKs), proxies, and miscreants using your home network to send spam.