Spamhaus
| The Spamhaus Project | |
|---|---|
| Type | Not-for-profit organisation (Spamhaus Project SLU)[2] |
| Founded | 1998, London[1] |
| Founder | Steve Linford[1] |
| Based in | Andorra (originally London)[1] |
| Commercial partner | Spamhaus Technology Ltd, London[2] |
| Focus | IP and domain reputation; DNS blocklists (DNSBLs) |
| Free datasets | SBL, XBL, PBL, CSS, ZEN, DBL, ZRD, DROP and others[1][6] |
| Website | spamhaus.org |
| Related | Blocklist check and delisting, Top domain extensions |
The Spamhaus Project is a not-for-profit organisation that tracks spam, phishing, malware and botnet infrastructure and publishes the results as reputation data for domain names and IP addresses. Its best-known products are DNS-based blocklists (DNSBLs): lists that a mail server can consult with an ordinary DNS lookup to decide whether to accept a message. It was started in London in 1998 and is now based in Andorra; large-volume and commercial access to its data is sold by a separate company, Spamhaus Technology.[1][2]
For domain owners, Spamhaus matters for one practical reason: if a domain appears on its Domain Blocklist (DBL), messages that mention or come from that domain are likely to be rejected or filtered by a large share of the world's mail systems, and some network security tools will block access to it. WikiForDomains is not connected with Spamhaus; this article summarises its public documentation.
History
Spamhaus was founded in 1998 to track IP addresses sending unsolicited bulk email and to publish them in a blocklist that email administrators could use for filtering. The name is a mock-German coinage for a provider that sends spam or knowingly hosts spammers.[1][2] Over time its research widened from spam to phishing, malware, ransomware and botnet command-and-control (C&C) servers, and from IP addresses to domains and autonomous systems. It added the Domain Blocklist in March 2010.[2]
Real-time delivery of the data at high volume is handled by Spamhaus Technology, which also runs the free key-based query service on the Project's behalf. In recent years the organisation has published research jointly with the Swiss malware-tracking project abuse.ch under the name Spamhaus-abuse.ch Alliance.[1][7] Spamhaus has received awards including the FBI-linked National Cyber-Forensics and Training Alliance's Cyber Crime Fighter Award and the UK ISPA's Internet Hero award (2003).[1]
Blocklists
Each list targets a different kind of identifier or behaviour. Mail software usually queries more than one.
| List | Lists | Typical use |
|---|---|---|
| SBL (Spamhaus Blocklist) | IP ranges researchers have tied to spam operations, spam-support services and other malicious activity | Reject connections from known bad networks |
| CSS (Combined Spam Sources) | Automatically detected IPs sending low-reputation mail, including snowshoe spam; part of the SBL | SMTP filtering |
| XBL (Exploits Blocklist) | Compromised machines: malware-infected hosts, open proxies, botnet members | Block mail and logins from hijacked devices |
| PBL (Policy Blocklist) | End-user and other IP space that should not send mail directly to other networks' mail servers, much of it supplied by the networks themselves | Reject direct-to-MX mail from home connections |
| ZEN | A combined zone of SBL, CSS, XBL and PBL; one query returns every matching code | Single IP lookup for mail servers |
| DBL (Domain Blocklist) | Domains and hostnames with poor reputation: spam, phishing, malware, botnet C&C, plus compromised ("abused-legit") hosts and abused redirectors | Check sender domains and links inside messages |
| ZRD (Zero Reputation Domains) | Newly registered or newly observed domains, each listed for 24 hours | Treat brand-new domains with extra caution |
| DROP (Don't Route Or Peer) | Network blocks wholly controlled by criminals | Firewall and router drop lists |
Spamhaus notes that ZEN contains only IP-based lists and gives no protection against bad domains, so the DBL must be queried separately by software that extracts domains from message headers and bodies.[4][5] The ZRD reflects an observation that new domains are rarely used for legitimate mail in their first day.[6]
How DNSBL lookups work
A DNSBL is published as a DNS zone, a convention later documented in RFC 5782.[8] To test an IPv4 address, the receiving server reverses its four octets and appends the zone name: a message from 192.0.2.25 becomes a lookup for 25.2.0.192.zen.spamhaus.org. To test a domain, the name is prefixed to the domain zone, as in example.com.dbl.spamhaus.org. If the name does not exist (NXDOMAIN), the item is not listed. If the lookup returns an address in the 127.0.0.0/8 range, the item is listed and the final octet says why.[4]
| Answer | Meaning |
|---|---|
127.0.1.2 | Spam domain |
127.0.1.4 | Phishing domain |
127.0.1.5 | Malware domain |
127.0.1.6 | Botnet C&C domain |
127.0.1.102 to 127.0.1.106 | Legitimate domain whose host has been abused (spam, redirector, phishing, malware, C&C) |
127.255.255.254 | Error: query arrived through a public resolver; not a listing |
127.255.255.255 | Error: too many queries; not a listing |
Because the DBL supports wildcard lookups, querying any hostname under a listed domain returns the domain's code. Spamhaus provides dbltest.com as a permanently listed test domain and recommends checking that answers fall within 127.0.1.0/24 before treating them as listings.[4]
Effect on email deliverability
Spamhaus publishes data; it does not block anything itself. Each receiving network decides how to act on a listing. Common policies are to refuse the message during the SMTP conversation (the sender sees a bounce that names the list), to accept it into a spam folder, or to add the listing to a spam score alongside other signals. Because Spamhaus says its data protects billions of mailboxes, a DBL or SBL listing tends to cause bounces at many unrelated providers at once.[1]
A domain does not need to send mail to be affected. The DBL is checked against links in message bodies, so a listed domain can cause newsletters, invoices or forum notifications that merely link to it to be filtered. Correct SPF, DKIM and DMARC records do not prevent a listing: Spamhaus points out that spammers can publish those records too, and that domains are listed with and without them.[4] The practical steps for a listed domain are covered in How to check if your domain is on a blocklist and get it delisted.
Use beyond email
- DNS firewalls. Domain data can be loaded into a Response Policy Zone (RPZ) so that a network's resolvers refuse to resolve known phishing, malware and C&C domains for users.[4]
- URL shorteners and comment systems. Spamhaus recommends that shorteners check every target domain against the DBL, and the list can flag spam links in blog comments and guestbooks.[4]
- Security products and threat intelligence. Commercial feeds and the Spamhaus Intelligence API supply domain and IP reputation to security platforms.[10] Web browsers generally rely on their own warning lists rather than querying Spamhaus directly, but a domain abused for phishing often ends up on several independent lists.
Free and commercial access
The public mirrors (for example zen.spamhaus.org) may be used free of charge only for low-volume, non-commercial use, and not through public DNS resolvers or from IPs with generic reverse DNS; such queries receive the 127.255.255.254 error instead of real data.[5] Users who query through a shared resolver can apply for a free key-based account, now called Blocklists via DNS Query (formerly the Data Query Service, DQS), whose terms limit it to non-commercial small organisations and individuals making no more than about 100,000 queries a day. ISPs, commercial spam-filter services and larger users need a paid subscription.[9] A six-month Intelligence API developer licence (5,000 queries a month) is offered for evaluation, not production.[10]
Domain reputation reports and most-abused TLDs
Twice a year Spamhaus publishes a Domain Reputation Update ranking top-level domains (TLDs) by the number of domains it listed as malicious or suspicious. The edition covering April to September 2026, published on 15 October 2026, counted 3.37 million such domains, up 56.6% on the previous six months, with September 2026 the highest month in its records at 1.15 million. Spamhaus attributed much of the rise to about one million cold-email domains listed after a data-sharing exercise with a deliverability firm, and repeated its view that cheap domains enable abuse at scale.[3]
| Rank | TLD | Type | Listings Apr–Sep 2026 | Oct 2025–Mar 2026 | Change |
|---|---|---|---|---|---|
| 1 | .com | gTLD | 724,149 | 506,482 | +43% |
| 2 | .top | gTLD | 627,907 | 270,121 | +132% |
| 3 | .cn | ccTLD | 465,270 | 252,852 | +84% |
| 4 | .vip | gTLD | 146,856 | 51,280 | +186% |
| 5 | .info | gTLD | 131,578 | 37,786 | +248% |
| 6 | .cc | ccTLD | 113,432 | 94,415 | +20% |
| 7 | .shop | gTLD | 81,476 | 52,350 | +56% |
| 8 | .xyz | gTLD | 65,463 | 47,547 | +38% |
| 9 | .icu | gTLD | 50,942 | 46,350 | +10% |
| 10 | .net | gTLD | 49,439 | 43,593 | +13% |
| 11 | .help | gTLD | 48,897 | new entry | n/a |
| 12 | .biz | gTLD | 47,522 | new entry | n/a |
| 13 | .ru | ccTLD | 45,472 | 54,612 | −17% |
| 14 | .cfd | gTLD | 44,502 | 93,940 | −53% |
| 15 | .org | gTLD | 42,534 | 31,057 | +37% |
| 16 | .bond | gTLD | 41,186 | 59,271 | −31% |
| 17 | .sbs | gTLD | 38,626 | 42,115 | −8% |
| 18 | .cyou | gTLD | 30,486 | 18,291 | +67% |
| 19 | .click | gTLD | 29,668 | 24,004 | +24% |
| 20 | .my | ccTLD | 26,949 | new entry | n/a |
Raw counts favour large zones: .com has by far the most registrations, so its share of abusive names is small. Spamhaus therefore also ranks TLDs by the percentage of their zone it lists, treating 5% as a red flag and anything above 10% as a clearly problematic TLD. In April–September 2026 three gTLDs exceeded 10%: .help (26.5%, largely cold email), .qpon (15.1%) and .study (12.4%); .vip was at 7.4%, .cfd at 7.0% and .top at 5.0%.[3]
| ccTLD rank | TLD | Listings | Change vs Oct 2025–Mar 2026 |
|---|---|---|---|
| 1 | .cn | 465,270 | +84% |
| 2 | .cc | 113,432 | +20% |
| 3 | .ru | 45,472 | −17% |
| 6 | .co | 18,179 | +221% |
| 8 | .uk | 13,298 | +99% |
| 10 | .de | 11,044 | +14% |
| 13 | .io | 5,908 | +169% |
| 17 | .eu | 3,740 | −38% |
Live, continuously updated TLD reputation scores are published on Spamhaus's reputation statistics pages.[11]
Controversies
Blocklist operators are periodically challenged by the senders they list. In 2006 the US bulk mailer e360 Insight sued Spamhaus in Illinois; Spamhaus disputed the court's jurisdiction, withdrew, and a default judgement of about US$11.7 million was entered, which Spamhaus said it would not recognise.[2] In March 2013 Spamhaus was the target of a large distributed denial-of-service (DDoS) attack that its DDoS-mitigation provider described as one of the largest publicly reported at the time.[12]
See also
- How to check if your domain is on a blocklist and get it delisted
- Top 25 domain extensions
- Cheap domains
- History of the Domain Name System
- Domain name lifecycle
- WHOIS lookup
References
- Spamhaus Project — Who is Spamhaus Project? (founding in London in 1998, now based in Andorra, free datasets, awards; retrieved 11 November 2026).
- Wikipedia — The Spamhaus Project (name origin, DBL launch in 2010, company structure, e360 case; retrieved 11 November 2026).
- Spamhaus — Domain Reputation Update, April–September 2026 (published 15 October 2026; PDF report).
- Spamhaus — FAQs: Domain Blocklist (DBL) (return codes, wildcards, test points, removal, RPZ, URL shorteners).
- Spamhaus — FAQs: How you can use the free Spamhaus blocklists.
- Spamhaus Technology — Blocklists via DNS Query, free account (datasets included, ZRD 24-hour window).
- Spamhaus Technology — About us (Spamhaus-abuse.ch Alliance).
- RFC 5782 — DNS Blacklists and Whitelists (IETF, February 2010).
- Spamhaus Technology — Terms of Use (Fair Use Policy) for Blocklists via DNS Query, free account (retrieved 11 November 2026).
- Spamhaus Technology — Intelligence API Developer License.
- Spamhaus — Reputation statistics (live TLD scores).
- Cloudflare blog — The DDoS that almost broke the Internet (March 2013).