Article
What Is the Spamhaus DBL? Domain Blocklist Explained
By Unlimited Verifier Team ·

Summary
The Spamhaus Domain Block List (DBL) is a DNS-based blocklist of domain names seen in spam, phishing or malware. Mail filters check the domains in a message's links, images and sender fields, so a listed domain can hurt delivery even when your sending IP is clean.The Spamhaus Domain Block List (DBL) is a DNS-based blocklist of domain names, not IP addresses, that have appeared in spam, phishing or malware messages, so a listed domain can hurt delivery even when your sending server is clean. Mail filters check it by domain name, usually the links, image hosts and sender domains in a message.
The DBL works differently from the better-known IP blocklists. Those ask which server sent a message. The DBL asks which domains appear in it. That is why a clean IP can still get hit, and why the fix often sits outside the mail server. For the wider picture, see our pillar on spam traps and email blacklists.
Quick answer
- What it is: A domain blocklist run by Spamhaus, queried through DNS as
yourdomain.dbl.spamhaus.org. - What it lists: Domains seen in spam, phishing and malware, including legitimate domains that spammers have abused.
- Why it matters: A listed domain in your links, tracking or sender fields can reduce inbox placement even when your sending IP is clean.
- What to do: Check every domain your recipients can see or click, fix the source of any listing, then request removal through Spamhaus.
What is the Spamhaus DBL, and how is it different from the other Spamhaus lists?
The DBL is the Spamhaus dataset that indexes domain names. Spamhaus's other main lists index IP addresses, which is where most of the confusion starts.
| Dataset | What it identifies | Typical reason for a listing | Who it affects |
|---|---|---|---|
| SBL | IP addresses and ranges tied to spam operations | Known spam sources | Senders on listed IPs |
| XBL | IPs of compromised or exploited machines | Malware, open proxies, hijacked hosts | Senders whose hosts are exploited |
| PBL | IP ranges that should not send mail directly | Dynamic or end-user connections | Mail sent straight from residential or dynamic IPs |
| DBL | Domain names in spam, phishing or malware | Domain appears in message content or sender fields | Any sender whose content or domains are listed, regardless of IP |
We cover the IP-based lists in Spamhaus SBL vs XBL vs PBL explained, and the IP-side causes in 8 reasons your IP address is blacklisted.
Bottom line: The DBL judges domains, so you can be listed with a clean IP, and an IP fix will not clear a domain listing.
What do the DBL return codes mean?
A listed domain returns an address in the 127.0.1.x range, and the last octet tells you why. Spamhaus documents these codes, and the table reflects the set described in its public documentation at the time of writing. Check Spamhaus's current documentation before acting, because codes can change.
| Return code | Meaning | What to check first |
|---|---|---|
| 127.0.1.2 | Spam domain | Content and sources that put this domain in your mail |
| 127.0.1.4 | Phishing domain | Urgent. Look for account or site compromise |
| 127.0.1.5 | Malware domain | Hosted scripts, downloads and third-party embeds |
| 127.0.1.6 | Botnet command-and-control domain | Hosting for signs of compromise |
| 127.0.1.102 | Abused legitimate domain: spam | A hijacked site or abused service you may not control |
| 127.0.1.103 | Abused spammed redirector | Redirect or shortening services used to hide spam destinations |
| 127.0.1.104 to 127.0.1.106 | Abused legitimate domain: phishing, malware or botnet | Same as 127.0.1.102, with a more serious abuse type |
The "abused legitimate" codes surprise businesses most. Your domain can be listed because someone else abused it, such as a compromised form that started injecting spam links into your site. In that case the fix is cleaning the site, not changing your mailing practices.
Bottom line: The code tells you whether the problem is your content, a compromise, or a legitimate domain used by others, and each needs a different fix.
How do you check whether a domain is on the Spamhaus DBL?
You check by making a DNS lookup for the domain followed by .dbl.spamhaus.org. A 127.0.1.x answer means listed, an NXDOMAIN answer means no record exists (not listed, as defined in RFC 1035), and a 127.255.255.x answer means the query was refused.
- Listed: The response is an address such as 127.0.1.2.
- Not listed: The response is NXDOMAIN.
- Refused or error: The response is an address in 127.255.255.x. This is not a listing. It usually means the resolver you used is not permitted to query the DBL.
The refusal case is where most false results come from. Many public DNS resolvers are not permitted to query the DBL, so a result from a public resolver can mislead you. Query through your own network's resolver or a resolver Spamhaus accepts.
Bottom line: A lookup is one DNS query, but a result only means something when it comes back through an accepted resolver.
Can you check the Spamhaus DBL for free?
Yes, for low-volume, non-commercial checks. Spamhaus's public query access is intended for limited use, and commercial or high-volume checking generally requires its paid Data Query Service. Check Spamhaus's current usage terms before you build checks into a production system.
For one-off checks, you do not need a paid service. Unlimited Verifier offers a free domain blacklist checker (listed in our comparison of blacklist checkers), and the free email checker handles single addresses. For automated, ongoing checks, plan for Spamhaus's terms rather than assuming free access will scale.
Bottom line: Free lookups are fine for audits, but automated checking at volume is a licensing question, not just a technical one.
Why do legitimate senders end up on the DBL?
Legitimate senders usually end up listed because of a domain they don't think of as their own sending domain. Public Spamhaus guidance and common listing patterns point to five causes:
- Shared click-tracking domains. Many ESPs route links through a tracking domain shared by customers. If another customer's content gets listed, that shared domain can carry the reputation into your sends. The fix is a custom tracking domain you control.
- Compromised landing pages or forms. A hijacked page or form that injects spam links can get your domain listed as abused (the 127.0.1.102 to 127.0.1.106 family). The fix is cleaning the site and keeping evidence.
- Harvested or purchased lists. These produce complaints and spam-trap hits, and the content sent to them can carry domains that later get flagged. We explain the mechanics in how spam traps get on your email list. The fix is to stop mailing the list and verify what remains.
- Partner and affiliate links. A link to a partner's domain that is itself abused puts that listing under your campaign. You can't clear their listing, so remove the link until they fix it.
- Redirectors and shorteners. Generic redirect services are a common route for spam, which is why 127.0.1.103 exists. The fix is direct links or a redirect domain you control.
Unsubscribe, image and tracking domains are easy to miss because recipients never see them as links. Audit them as carefully as the links people click.
Bottom line: Audit every domain your recipients can see or click, not just the one in your From address.
Does a Spamhaus DBL listing block your email?
Not automatically. A DBL listing is one signal among many. Spamhaus does not publish how much weight a listing carries, and each receiving system sets its own policy. SpamAssassin, the open-source filter, includes DBL-based URI rules that add to a message's spam score, and other filters use the list in their own ways.
The bigger risk is quiet. DBL problems often appear as lower inbox placement and more complaints rather than as hard bounces. ESP dashboards are built around bounces, so a listed tracking domain can leave the bounce rate looking normal while delivery drops. Complaint trends are the metric to watch: Google's bulk-sender guidance asks senders to keep spam rate in Postmaster Tools below 0.10%, and warns against approaching 0.30%, according to its sender guidelines. If complaints rise after a template change, run a DBL lookup on that template's domains.
Bottom line: Treat a listed domain as a deliverability problem even when no bounce error appears.
How do you get removed from the Spamhaus DBL?
You get removed by fixing the source of the listing and then requesting removal through Spamhaus's lookup page. Spamhaus assesses the request under its own policies and does not guarantee a timeframe, so fix the cause first or the listing will likely return.
- Read the code. A 127.0.1.2 points to content, while 127.0.1.102 to 127.0.1.106 point to abuse of a legitimate domain.
- Find the source. Check your sending and tracking domains, image hosts, unsubscribe links, partner links and any landing pages you control.
- Fix it and keep evidence. Remove spam links, patch the compromised form or site, stop the harvested list, and keep logs or screenshots of the fix.
- Request removal through Spamhaus once the source is gone.
- Monitor the domain for several weeks. A listing that returns quickly usually means something in the source is still live.
If the listed domain belongs to a partner, they need to fix their site and request removal. Your job is to take the link out of your sends until they do. Be wary of third-party services that promise guaranteed delisting for a fee. Spamhaus's own process is the authoritative route. Our guide on how to get removed from the Barracuda blacklist shows how removal differs between lists.
Bottom line: Removal verifies a fix, so fix the source before you ask for it.
How long does a DBL listing last?
Spamhaus does not publish a fixed duration. A listing is tied to the status of the source domain, so a domain whose abuse has stopped can clear, while one still producing abuse will be listed again. If a listing persists after you have cleaned the source, check for live spam paths you missed, such as an old form, an old landing page or a forgotten redirect.
Bottom line: Duration depends on the source, so the source is what you control.
How does the DBL compare with SURBL and URIBL?
The DBL, SURBL and URIBL all check domains found in mail, but each uses its own listing criteria, categories and usage terms. A domain can be clean on one list and listed on another, so mail systems often check several at once.
| Blocklist | What it indexes | Distinctive features | Notes for senders |
|---|---|---|---|
| Spamhaus DBL | Domains in spam, phishing and malware, including abused legitimate domains | Return codes distinguish spam, phishing, malware, botnet and abuse of legitimate domains | Its codes tell you whether the cause is your content or a compromise |
| SURBL | Domains found in URLs within spam messages | Organises listings into category lists (for example, spam, phishing and malware) | Check its current list documentation to see which categories your filter uses |
| URIBL | Domains and URIs associated with spam | Publishes black, grey and red lists with different confidence levels | Check its usage terms, since free-use rules differ from Spamhaus's |
Descriptions reflect each provider's public documentation and may change. Confirm current criteria with each provider.
Bottom line: Check the DBL alongside SURBL and URIBL, because a clean result on one list does not mean clean on all of them.
Where does email verification fit in?
Email verification and the DBL answer different questions. Verification asks whether each recipient address is deliverable. The DBL asks whether the domains in your message are flagged. A clean verification result tells you nothing about DBL status, and a clean DBL check tells you nothing about your list.
Unlimited Verifier checks the recipient side: syntax, domain, MX records and the SMTP mailbox, with catch-all detection and flags for disposable and role-based addresses. Results sort into Valid, Risky and Invalid. Standard verification is unlimited on every plan, including Free, so the limits to plan around are on deep verifications. Free includes 750 deep verifications a month, and Pro includes 25,000. When you compare best email verification tools, check how each one handles this distinction. Our how to choose an email verifier guide covers the criteria in more depth.
Verification also helps with the list-side causes of DBL trouble. Removing invalid and disposable addresses can reduce the spam-trap and complaint pressure that often comes with harvested data, which we cover in 5 ways to avoid hitting spam traps. For ongoing hygiene, see email list maintenance best practices and email verification compliance and hygiene.
Bottom line: Verify your recipients and check your domains. They are two separate audits, and you need both.
How do you run a DBL audit for your sending program?
Run the audit in this order: content domains first, then tracking and infrastructure, then recipients. Fixing the list while a listed domain keeps hurting every send wastes the effort.
- Inventory every domain in your templates, including links, images, tracking, unsubscribe and partner URLs.
- Look up each domain against the DBL through a resolver Spamhaus accepts.
- Classify each result by return code, using the table above.
- Fix the sources for any listed domain, and replace shared or abused domains where you can.
- Verify the recipient list before the next send, so the send itself doesn't add risk. For new signups, real-time validation stops bad addresses at entry.
- Re-check the domains after fixes and again before each major campaign.
- Record the results with dates, so you can show when a listing appeared and when it cleared.
For SaaS teams sending product updates at volume, the same audit fits into a standard workflow. See email verification for ecommerce and SaaS for how teams fit verification into recurring sends.
Bottom line: Audit the domains you control first, then the people you mail, and repeat the domain check whenever a template changes.
Hands-on tutorial: audit a campaign's domains and recipient list
This takes about an hour for a typical campaign and needs no coding.
- Export your template as HTML. Save the campaign from your ESP as an HTML file and open it in a text editor.
- Pull out the domains. Search for
href=andsrc=, then copy each domain into a spreadsheet column. Include unsubscribe and tracking links. - Remove duplicates. Keep one row per domain. The same tracking domain often appears dozens of times.
- Look up each domain. On macOS or Linux, run
dig +short example.com.dbl.spamhaus.org. On Windows, runnslookup example.com.dbl.spamhaus.org. Replaceexample.comwith each domain. - Read each result. NXDOMAIN means not listed. A 127.0.1.x address means listed, so check the code. A 127.255.255.x address means the query was refused, so switch to an accepted resolver before drawing conclusions.
- Export your recipient list. Download a CSV of the contacts you plan to send to, with the email column included.
- Verify the list. Go to upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, each list can hold up to 25,000 emails, so split larger files first.
- Sort the results. Remove Invalid addresses, hold back Risky ones, and send only to Valid contacts. Risky results include catch-all domains, which accept every address, so their mailboxes can't be confirmed. The catch-all email verification page explains how these are handled.
- Export and save the results. Export as CSV, Excel or JSON. Results are kept for 24 hours on Free and 30 days on Pro, so save your files rather than relying on the platform.
- Re-import the Valid segment into your ESP, add the Invalid addresses to its suppression list, and repeat the DBL lookup after fixes. Record the date and results.
To check one address before deciding what to do with it, use the free email checker.
Bottom line: Ten steps cover both the content side and the recipient side, so one hour of work covers the whole audit.
Worked example: a 40,000-contact campaign with two listed domains
The numbers below are hypothetical, and the domains are placeholders. The arithmetic and plan limits are real.
The setup: A SaaS company sends a product update to 40,000 contacts. The template links to six domains: its sending domain, a shared ESP tracking domain, an image CDN, a product-page domain, an unsubscribe domain, and a partner's domain. The partner link appears only in a module shown to 30% of recipients.
The findings:
- The shared tracking domain returns 127.0.1.2 (spam).
- The partner domain returns 127.0.1.102 (abused legitimate domain), meaning its site was hijacked.
Exposure: Every link routes through the tracking domain, and the partner link appears in part of the send.
Tracking domain: 40,000 × 100% = 40,000 messages carry the listed domain
Partner domain: 40,000 × 30% = 12,000 messages carry the listed domain
The tracking domain is the higher priority, even though both are listed.
The fix:
- Move click tracking to a custom domain you control, and confirm it returns NXDOMAIN before the next send.
- Remove the partner link from the template. The company cannot clear the partner's listing, so it waits for the partner to fix their site.
- Verify the list. On the Free plan, verification is capped at 25 lists of up to 150 emails each per month, which is 3,750 addresses. That is 40,000 ÷ 150 = 266.67, so 267 lists, and 267 ÷ 25 = 10.68 months of allowance. Free is not practical for this list. On Pro, the list splits into 25,000 + 15,000 = 40,000. Standard verification is unlimited on Pro, so there is no per-email fee. Pro costs $29 a month, or $25 a month billed annually, which is $300 a year.
- Re-check through the API. Pro includes 100,000 API emails a month. Sending the 40,000 addresses in batches of up to 10,000 per request takes four requests per round. Two rounds (before and after fixes) use 80,000 emails and leave 20,000 for the month. See the email verification API and our note on email verification API and automation for how to script the workflow.
The send rule: Hold the campaign until both domains return NXDOMAIN on re-check. If either still returns 127.0.1.x, do not send.
Bottom line: Audit by reach, not by which listing code looks worst. A listed domain on every link outweighs a listed domain in a single module.
Common mistakes
- Fixing the IP and ignoring the domain. A clean IP will not clear a listed tracking or content domain.
- Checking only your From domain. Tracking, image, unsubscribe and partner domains are the usual blind spots.
- Reading 127.255.255.x as clean or listed. It is a refusal, so check the resolver before trusting the result.
- Requesting removal before fixing the source. The listing returns, and you lose credibility for the next request.
- Paying for guaranteed delisting. Spamhaus's own process is the authoritative route, and no third party can override it.
- Waiting for bounce alerts. Listings often cut inbox placement without producing bounces, so monitor complaints and placement too.
- Assuming verification covers domain blocklists. Mailbox verification and DBL lookups answer different questions.
- Buying lists and then wondering why domains show up. Harvested data drives both spam-trap hits and domain trouble.
Bottom line: Most DBL problems come from checking the wrong domain, misreading the result, or asking for removal too early.
How we compared (and limitations)
This article is based on public documentation: Spamhaus's published descriptions of its lists and return codes, RFC 5782 on DNS blacklists and whitelists, Spamhaus's public information on its query services, and the public documentation of filters such as SpamAssassin. The worked example uses hypothetical numbers and placeholder domains.
Neither Spamhaus's removal review process nor the policies of individual receiving systems are fully public, so this article does not describe how any specific system weighs a listing. Return codes, usage terms and provider criteria can change, so confirm them with Spamhaus, SURBL, URIBL and your ESP before you automate checks.
Unlimited Verifier's plan details are the company's own published information. Its 99.5% accuracy figure for deep verification is the company's stated figure, not an independent benchmark. Unlimited Verifier's bulk verification covers the mailbox and domain checks described above, so run a domain blacklist check separately using the free domain blacklist checker.
Bottom line: Use the codes and limits here as a starting point, and confirm current behaviour with Spamhaus and your ESP before you act.
DBL triage steps
- List every domain in the message: From domain, links, image hosts, tracking domains.
- Query each one at domain.dbl.spamhaus.org.
- Note the return code (127.0.1.2 spam, 127.0.1.4 phishing, 127.0.1.5 malware, 127.0.1.102+ abused legitimate).
- Find the source: compromised site, abused redirect, spammy content, or third-party embed.
- Fix the source and remove or replace the affected domain.
- Request removal through Spamhaus once the problem is resolved.
- Re-check the domain and monitor delivery for several sends.
Frequently asked questions
How do I check if my domain is on the Spamhaus DBL?
Query the DNS name yourdomain.dbl.spamhaus.org. If it resolves to a 127.0.1.x address, the domain is listed, and the last octet indicates the reason. If it returns NXDOMAIN, the domain is not currently listed. Use a DNS lookup tool or your mail platform's blocklist checker.
Can a clean IP address still be listed on the DBL?
Yes. The DBL indexes domains, not IP addresses. If a domain in your links, tracking URLs or sender fields appears in spam or phishing, it can be listed even when your sending server has a clean reputation.
How do I get removed from the Spamhaus DBL?
Fix the underlying cause first, such as a compromised site, abused redirect or spammy content. Then submit a removal request through Spamhaus's lookup and removal tools. Listings tied to an active problem are generally not removed until the problem is resolved.
Does the DBL affect Gmail or Microsoft delivery?
Spamhaus lists are used by many mail filters and providers, but each receiver sets its own policy and does not publish exactly how it weighs DBL hits. A DBL listing can reduce inbox placement at some receivers, so treat it as a real risk to fix.
What is the difference between the DBL and the ZEN list?
ZEN is Spamhaus's combined IP blocklist that merges SBL, XBL and PBL data. The DBL is a separate dataset that indexes domain names. Checking ZEN tells you about sending IPs, while checking the DBL tells you about domains in message content.
Can a legitimate domain be listed on the DBL?
Yes. Codes in the 127.0.1.102 to 127.0.1.106 range are used for legitimate domains that spammers or attackers have abused, such as hijacked sites or misused redirect services. The owner may not have caused the problem but still needs to clean it up.
Which domains does the DBL check in an email?
Mail filters typically check domains found in the message body, links, images, and sender-related fields such as the From or envelope domain. Each receiver chooses which fields it inspects, so audit every domain a recipient can see or click.
How long does a DBL listing last?
There is no fixed duration published for every listing. Listings are generally tied to the activity that caused them and can be removed after the source is fixed and the listing is reviewed. Check Spamhaus's current documentation for the latest policy.
Is the Spamhaus DBL free to use?
Spamhaus offers free public queries for low-volume use, but high-volume or commercial use typically requires a paid data query service. Check Spamhaus's current terms to confirm which usage tier applies to you.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.