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)
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 a parter
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.
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 XYZ and Sarah Miller on 10 Mar 2022
In part two of our Registries Series, we’re still in discussion with XYZ. Previously in Getting the low-down from XYZ on combating domain abuse, we talked about the what, why, and how of domain abuse. However, when XYZ was chatting about domain suspensions, they mentioned how anonymizing registrant details was an added challenge.
The redaction of domain ownership information, as a result of various privacy legislation, including GDPR, causes Spamhaus significant headaches at times, so we're interested to hear why it's an issue for Registries and what they're proposing to readdress the balance between those wanting to abuse the internet and those wanting to protect it. Over to you XYZ…
XYZ: We left off our discussion talking about domain suspensions. However, for most registries, the reality of anti-abuse action on the domain name side is that the isolated action of shutting down a domain isn’t the most effective method of stopping cybercriminal activity. There needs to be collaboration across multiple areas.
Spamhaus: Can you explain why you feel this way?
XYZ: Firstly, it’s important to understand that a domain name is purely an address. An abusive website or file is uploaded to a hosting company, and an abusive domain user is the customer of a registrar. When a registry suspends a domain used as an address to an abusive website or file, an abusive user can simply find another address to use. This is why abuse is not domain extension-specific. The abusive user can connect their malicious files to another domain extension to facilitate the abuse again in a matter of minutes.
Secondly, registries like XYZ have no direct contact with registrants. Their only course of action is to suspend the domain and notify the registrar. This doesn’t stop the bad actor; it just redirects them to other domain extensions. For these reasons, XYZ strongly believes that the registry, registrar, and cybersecurity organizations should work together.
Spamhaus: How do you think these relationships should interact in a perfect world?
XYZ: If all parties act in harmony, we can help break the cycle of abuse and more effectively prevent cybercriminal activity. When the XYZ Registry receives evidence of abuse from cybersecurity experts, we verify and suspend the domain and then notify the relevant registrar of their customer’s suspension. The registrar can prevent the abusive customer from registering further domains. It is the least effective method to start at the registry level since that is not the source of the malicious file or user. Still, the XYZ Registry is very active and successful in doing what we can to slow down bad actors and move them off .xyz.
Spamhaus: What do you think can be done to help this cross-section of the industry work more effectively together?
XYZ: An important aspect of rapid abuse control is being able to identify a group of domains registered by the same bad actor, so all domains under their control can be investigated. One of the most apparent innovations would be greater visibility into this association. At this time, only a registrar can determine what other domains an abusive user has in their account.
At the registry level, we can use the time of registration to associate multiple registrations occurring at the same registrar; however, this is not a silver bullet. With a domain as popular as .xyz, there are many instances of domains registered with the same timestamp by multiple legitimate registrants. To avoid false positives, we can only use this methodology to monitor closely.
An innovation in associating domains, users, and accounts used for abuse while maintaining data privacy, could help organizations better track the movement of bad actors across platforms and services.
Spamhaus: We strongly support this idea. From our perspective, one of the often-overlooked uses of the data that “Whois” published is “correlation,” not “identification.” Bad actors often use stolen or fake identities. While the actual information from the records won’t always lead to a real-world attribution, it does enable our researchers to make important associations.
Meanwhile, legitimate domain owners suffer due to this data redaction – it is increasingly hard to determine if a newly registered domain belongs to a known entity with a good reputation.
A cross-platform method of information association wouldn’t solve all the issues introduced by ownership redaction. Still, we feel that it would undoubtedly go a long way towards improving the situation for both malicious and legitimate domains. The next question must be, who can make this happen? Perhaps one for ICANN?
Next in our series, XYZ dives into the world of newly registered domains and email.
30 March 2022
fTLD, the registry behind .bank, turns to Passive DNS to ease the burden of compliance.
23 March 2022
Here, fTLD, the registry for .bank and .insurance top-level domains (TLDs), provides their view of how a TLD can make it simple for users to trust their interactions with websites.
16 March 2022
Here are some key considerations regarding the proper processes and procedures when sending email using a newly acquired domain name.