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.
Data for Integration
Enhance your service and create competitive advantage by integrating Spamhaus’ world-class IP and domain reputation data.
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) Firewall
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.
abuse.ch Real Time Feeds - coming soon
Actionable data signals on cyber threats, with a focus on malware and botnets, to strengthen threat investigations, detections, and help prevent data breaches.
Integration | MDaemon
Block over 99% of email-borne threats with Spamhaus’ real time DNS blocklists and MDaemon® Email Server.
Integration | Halon
Safeguard your email stream using Spamhaus’ real time DNS blocklists and Halon’s secure email infrastructure.
Integration | Messageware
Enhance Microsoft Exchange protection by blocking malicious IP addresses from connecting to your on-premise server in real time.
A wide range of datasets, providing multiple layers of protection. They can be plugged directly into your existing hardware, making them an affordable choice.
Exploits Dataset Statistics
View the geolocation, hosting network, malware names associated with each detection, and other critical data points.
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.
abuse.ch Threat Intelligence Feeds – coming soon
URLhaus, MalwareBazaar, ThreatFox, YARAify, Feodo Tracker and Sandnet enrich CTI feeds and support vulnerability mangement.
Find out more about us.
Learn more about Spamhaus; who we are, and what we do.
Find a partner
Discover our partners and how they can support you.
Become a partner
Learn about the benefits of being a Spamhaus partner and how to get started.
Discover a wide range of blog posts, case studies and reports.
Spamhaus’ insight into malware, botnet C&Cs, and the domain reputation landscape.
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.
The Reputation Portal
A tool for ASN owners to get visibility of their IPs’ reputation and proactively manage listings.
Help for the Project's legacy DNSBLs users
Using the Project’s legacy blocklists 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 Carel Bitter on 25 Jul 2023
In May 2023, ICANN proposed a set of amendments to registry and registrar contracts (commonly known as the RA and the RAA) with an aim of targeting DNS abuse more effectively. This shift towards a more proactive approach signifies a crucial step towards mitigating internet abuse and cybercrime. The call for comments regarding these amendments is now closed. Learn more about the changes, and our answer to the question – "Are they enough?"
For many years Spamhaus has maintained that registries and registrars play a vital role in mitigating, disrupting, and preventing various forms of internet abuse, cybercrime, and many other types of malicious activity. After all, many of these activities depend on the availability of at least one domain name to complete the chain of events that leads to the bad actor’s desired outcome. Whether it’s regular phishing, malware delivery, or more advanced activities like state-sponsored espionage, somewhere there is a domain name in play. Without one, these efforts often just cannot succeed.
In the gTLD space (generic names, as opposed to country-specific names), the ICANN Registry Agreement (RA) and 2013 Registrar Accreditation Agreement (RAA) govern everything related to a domain names’ lifecycle. The ICANN Organization has published a series of proposed amendments for these contracts, specifically dealing with DNS Abuse. DNS abuse in this case is defined as malware, botnets, phishing, pharming, and spam (in such cases wherein spam is used to deliver the previously mentioned forms of DNS abuse). We believe these amendments are a step in the right direction.
In essence, the amendments look to strengthen obligations that require registrars and registries to stop or otherwise disrupt DNS abuse. From making abuse contacts readily accessible, to providing clarity around DNS abuse definition, to recognition of the different roles of registrar and registries (you can read an overview of the proposed amendments here).
There is one change, however, that on the surface seems simple, but has the potential to make a big difference. Under the newly proposed amendments, where DNS abuse is identified and a report is actionable, a registrar must:
Promptly take the appropriate mitigation action(s) that are reasonably necessary to stop, or otherwise disrupt, the Registered Name from being used for DNS Abuse. (Excerpt taken from the proposed RAA section 3.18.2)
While this may seem obvious, and in a sense, an expected behavior in 2023, the current version of the contract is much less clear about taking action on reports of DNS abuse:
Well-founded reports of Illegal Activity submitted to these contacts must be reviewed within 24 hours by an individual who is empowered by Registrar to take necessary and appropriate actions in response to the report. (Excerpt from the current 2013 RAA section 3.18.2)
In other words, while the current contract requires reports to be reviewed, the new contract requires action. It may seem like a small and even obvious change, but it has taken a long time to get here. At last, once the proposed changes to the RAA come into force, registrars who fail to act upon mitigating malicious domain names that they sponsor will be in breach of the RAA, allowing ICANN Contractual Compliance to investigate.
Of course, they could! The meaning of terms like ‘prompt’, ‘reasonably necessary’ and ‘disrupt’, could be debated endlessly; there are many open ended ‘what-ifs’ and ‘it-depends’ in this conversation. Also, how DNS Abuse is currently defined leaves room for many abusive or malicious activities to go unaddressed.
And we wouldn’t be Spamhaus if we didn’t point out that the DNS Abuse definitions around spam could be much stronger. After all, authentication plays a vital role in modern email. Common SMTP authentication standards, such as SPF, DKIM and DMARC, rely heavily on domain names.
For more detailed feedback, Spamhaus contributed to M3AAWG’s comments on the ICANN amendments, which can be accessed here.
To us, this is positive progress that both empowers and puts a burden on parties who play a big part in enabling many abuse-related activities. It is a given that the ICANN multi-stakeholder process generally moves at a slow pace – note that this is a small update to a ten-year-old contract. This speed of change is a stark contrast to the relentless churn of tactics and operations in internet abuse, cybercrime and the many other forms of online malicious activity.
Given the challenge afoot, it seems to us that perfect is the enemy of the good and we’d much rather have something good, right now.