Article
How to Check If Your Domain Is Blacklisted: Step-by-Step Lookup Guide
By Unlimited Verifier Team ·

Summary
To check if your domain is blacklisted, look up your sending IP and domains against major DNS blocklists such as Spamhaus, Barracuda and SURBL, using a web checker or a dig query. An answer in 127.0.0.0/8 means listed, and an empty answer means clean. Check after every large send, because listings can appear and clear within days.To check if your domain is blacklisted, look up your sending domain and sending IP address against the major DNS blocklists, including Spamhaus, Barracuda and SURBL, either with a free web checker or a single dig query. A listed result returns an address in the 127.0.0.0/8 range, and a clean result returns nothing.
One check is rarely enough. Listings can clear within days and are often tied to a single campaign, so the useful question is whether you were listed during your last send, not only whether you are listed today. This guide covers how to check each identifier, how to read the results, which lists deserve attention, and what to do when a listing appears. For the wider context, start with our spam traps and email blacklists guide.
Quick answer
- Check four identifiers, not one. Look up the sending IP, the From and Return-Path domains, the DKIM
d=domain and your link domains. A clean domain can still sit on a listed IP. - Use two methods. A web checker gives a fast overview. A
digquery against a list's DNS zone gives a repeatable answer you can script. - Read the response correctly. An empty answer means not listed. A 127.0.x.x answer means listed. A 127.255.255.x answer from Spamhaus means your query was refused, not that you are listed.
- Fix the trigger before requesting removal. Removal requests are often refused because the cause is still in place.
- Check after every large send. A weekly scripted check catches listings that appear and clear between monthly reviews.
What does it mean for a domain to be blacklisted?
A domain is blacklisted when a DNS-based blocklist (DNSBL) publishes a listing for it as a source of spam, phishing or malware. Receiving mail servers query these lists in real time, and a hit can lead to rejection, spam-folder placement or throttling.
RFC 5782 describes the model. A receiving server turns an IP address or domain into a DNS query, and the list answers with an address conventionally in 127.0.0.0/8 if the subject is listed. That is why you can check a listing with a DNS query, not only with a web page.
Three different problems get grouped under "blacklisted":
- IP listings apply to the server sending the mail. They are common on shared ESP infrastructure, where one customer's problem can affect every sender on the pool.
- Domain listings apply to the domain in your sender identity or in your message content, such as links, images and redirect URLs.
- Reputation drops involve no list entry at all. A filter treats your mail as risky, and the evidence appears in provider dashboards such as Google Postmaster Tools rather than in a lookup.
Gmail and Outlook.com don't publish a DNSBL you can query, as far as public documentation shows. Their filtering problems appear in their own dashboards, which is why a clean lookup doesn't prove clean delivery.
Bottom line: A blacklist is a DNS result, but you can have a delivery problem with no listing at all, so check both the lists and the provider dashboards.
Why do I need to check my domain and sending IP separately?
You need to check them separately because each list reads a different identifier in the message. A clean domain can ride on a listed IP, and a clean IP can carry a link to a listed domain.
| Identifier | Where to find it | Lists to check | Why it matters |
|---|---|---|---|
| Sending IP | Your ESP's account settings, or the Received header your outbound server added |
Spamhaus ZEN, Barracuda | Connection-level filters often judge the IP before reading content |
| From and Return-Path domain | Message headers | Spamhaus DBL, SURBL | The domain the mail claims to come from, and where bounces go |
DKIM d= domain |
The DKIM-Signature header |
Spamhaus DBL, SURBL | The domain that cryptographically signed the message |
| Link and image hostnames | The HTML of the campaign | SURBL, URIBL, Spamhaus DBL | Tracking and redirect hosts are frequently abused, and a listing can name a subdomain such as links. rather than the registered domain |
For SaaS teams, the IP check matters most for transactional mail. Password resets and invoices often share a pool with other customers, so one listing affects many senders. Marketing teams on a dedicated setup should focus on domain identifiers, because one bad campaign link can list the domain. Our guide to what causes an IP address to be blacklisted covers the IP side in more depth.
Bottom line: Check four identifiers, not one. Most missed listings come from the identifier nobody thought to check.
How do I check if my domain is blacklisted, step by step?
Gather your identifiers, run a web checker for a quick picture, confirm with a DNS query, check provider dashboards, and log the result with a date. Repeat this on a schedule, not once.
- Collect your identifiers. For the sending IP, open your ESP's account settings. If you send from your own server, use the
Receivedheader that your outbound server added when it sent the message. Send a test message to a personal inbox, open its raw headers, and confirm the DKIMd=domain and Return-Path. Add the exact hostnames of your tracking links. - Run a web checker. MXToolbox's blacklist check covers a large set of public lists in one lookup. Barracuda's and Spamhaus's own lookups check only their own lists, so use them to confirm specific hits. Record which lists returned a hit and the date.
- Run a DNS query for each list you monitor. This is the reliable, repeatable check, and the next section shows how.
- Check the provider dashboards. In Google Postmaster Tools, review your domain's spam rate and reputation (the domain must be verified, and data appears only with enough Gmail volume). For Outlook.com, register your IP through Microsoft's Sender Support portal to see SNDS data.
- Log the result. Keep a dated record of every hit and every clear. A listing that lasted two days and one that lasted two months point to different causes, and you can only see the pattern if you log it.
How do I run a DNS blocklist query myself?
A dig query asks the list directly, so it doesn't depend on a third-party website being up. For IP checks, reverse the octets of the address. For domain checks, use the domain as written.
# IP check on Spamhaus ZEN. 192.0.2.10 reversed is 10.2.0.192
dig +short 10.2.0.192.zen.spamhaus.org
# Domain check on Spamhaus DBL
dig +short yourdomain.com.dbl.spamhaus.org
An empty response means the subject is not listed. A 127.0.x.x response means it is listed, and the last octet tells you which part of the list fired. For example, Spamhaus's return-code documentation maps 127.0.0.2 to the SBL (spam source) and 127.0.1.2 to a spam-domain listing on the DBL. Check spamhaus.org for the current codes before drawing conclusions, because codes can change.
Don't run these queries through a public resolver, such as a public DNS service configured on a laptop or a default resolver in some cloud environments. Spamhaus returns 127.255.255.x error codes to queries from many public resolvers. If you see those, the test failed. Switch to your own resolver or use a web checker.
To monitor over time, wrap the queries in a short script that loops over your IPs and domains, writes the output to a dated log, and alerts you on any 127.0.x.x response.
Which method should I use?
| Method | What it covers | Speed | Limits | Best use |
|---|---|---|---|---|
| Web checker | Many public lists in one lookup | About a minute | Manual, one subject at a time | Quick spot checks |
DNS query (dig) |
Any list that publishes a DNS zone | Seconds, scriptable | Needs reversed IPs and correct zones; public resolvers can be refused | Scheduled monitoring |
| Google Postmaster Tools | Gmail spam rate and domain reputation | Ongoing; requires a verified domain | Shows data only with enough Gmail volume | Tracking trends |
| Microsoft SNDS | IP-level data for Outlook.com | Ongoing; requires IP registration | Covers Microsoft traffic only | Diagnosing Outlook.com problems |
Unlimited Verifier also offers a free domain blacklist checker, which is useful for a first look. It is a quick lookup, not a replacement for the DNS queries above, and our comparison of blacklist checker tools explains how the main checkers differ in scope.
Bottom line: Use a web checker to find out quickly, a DNS query to monitor reliably, and the provider dashboards to see the delivery impact of a listing.
How do I read the results?
A hit means the subject is on that list, but urgency depends on which list fired, whether the listing is for an IP or a domain, and whether your bounce and complaint data confirm a problem. Use this table to decide what to do.
| Result | What it usually means | Action | Urgency |
|---|---|---|---|
| No hits on the lists you monitor | Clean on those lists | Keep scheduled checks running | Low |
| One niche list | Limited impact on its own; may reflect one bad send | Trace the trigger and request removal where the list allows it | Medium |
| Spamhaus SBL, XBL or DBL | Widely used by filters, so impact can be broad | Pause risky segments, trace the trigger, request removal | High |
| Barracuda hit on the sending IP | Affects recipients behind Barracuda gateways | Follow the Barracuda removal guide, then review bounces and complaints | High |
| Google Postmaster spam rate of 0.30% or higher | Google's published warning line | Cut sends to unengaged contacts and suppress complaints | High |
| 127.255.255.x response | Your query was refused | Re-test from your own resolver or a web checker | Re-test first |
Google's sender guidelines recommend keeping user-reported spam below 0.10% and warn against reaching 0.30% or higher. Yahoo's sender requirements set a similar complaint-rate expectation, but the two don't publish identical framing. We recommend 0.10% as your working target and 0.30% as the line you must not cross.
Bottom line: Treat a Spamhaus or Barracuda hit as urgent, and treat a single niche hit as a signal to investigate, not an emergency.
Which blacklists should I check first?
Start with Spamhaus and Barracuda, because their listings are used by many filters and affect more of your mail. Then move to link-domain lists, which are usually the fastest to fix.
- Spamhaus (ZEN, DBL and SBL). ZEN covers IP listings, DBL covers domains, and SBL covers spam sources. The return code tells you which part fired, which narrows your investigation.
- Barracuda. Relevant if your recipients sit behind Barracuda gateways, which is common in education and enterprise. Its hits can look to users like random delivery failures, so you may hear about the problem from a recipient before your checks show it.
- SURBL and URIBL. These are domain-based lists aimed at URLs in message bodies. A hit points to a specific link host in your campaign, which makes it the quickest to diagnose and fix.
- Smaller and user-report lists. Some rely on spam reports from their own networks. A hit can still matter, but it is usually weaker evidence than a Spamhaus listing, so confirm it against your bounces and complaints first.
Removal rules differ. Some listings expire on their own, some need a request, and some need the cause fixed before they are lifted. Read each list's own policy before acting.
Bottom line: Fix Spamhaus and Barracuda hits first, and use link-domain hits as quick wins.
What should I do if my domain is listed?
Record the listing, find the trigger, fix it, request removal, and then recheck. Removing a listing without fixing the cause usually produces a second one.
- Record the details. Note the list, the return code, whether the identifier is an IP or a domain, and the time you first saw it.
- Find the trigger. Review the last 7 to 14 days of sending. Compare bounce and complaint rates by segment, and line up the listing date against any new link domain, template change or list import. Imported lists are a common source of spam traps, and seven signs your list contains spam traps can help you check for them. Our common reasons emails get blacklisted list covers other frequent triggers.
- Fix it. Remove invalid addresses, suppress complaints and unsubscribes, replace the flagged link host, and pause any segment that is still unverified.
- Request removal. Use the list's own process. Spamhaus and Barracuda both publish removal procedures, and both expect the underlying problem to be addressed first.
- Recheck on a schedule. Wait for the review period the list describes, then check daily for a week. Keep volume reduced until the listing clears and bounces stay low.
Some listings expire without any action. Your log will show whether yours did. Repeated removal requests with no change in sending behaviour are the most common reason removals stall.
Bottom line: Fix the trigger first, request removal second, and confirm the fix in your bounce and complaint numbers.
What does a real listing look like in numbers?
This example is illustrative. The arithmetic is accurate, and the verification results are hypothetical.
The situation: A B2B software company keeps a 14,000-contact list but mails only its 9,000 active contacts each week. Monday's check shows its sending domain on the Spamhaus DBL, while the sending IP is clean on ZEN. The last campaign to the 9,000 active contacts produced 412 bounces:
412 ÷ 9,000 = 4.58% bounce rate
That is well above the 2% working ceiling many teams set.
Tracing the cause:
- The DBL hit pointed to a tracking redirect host inherited from an agency template that had been live for six weeks.
- The bounce rate showed that the active segment contained dead addresses, and the team had no measure of the 5,000 inactive contacts.
Verification: On the Free plan, lists are capped at 150 emails, so this 14,000-row list needs a paid plan. The Pro plan at $29 a month allows lists of up to 25,000 emails, so the full list fits in one upload. Standard verification is unlimited on every plan. Deep verification on the full list uses 14,000 of the 25,000 monthly deep verifications, which leaves 11,000 for the rest of the month.
Hypothetical results:
- Valid: 11,480 (82.0%)
- Risky: 1,540 (11.0%), flagged as catch-all, disposable or role-based
- Invalid: 980 (7.0%)
Check: 11,480 + 1,540 + 980 = 14,000.
Of the 980 invalid addresses, 412 bounced in the last send. The other 568 were invalid addresses the campaign didn't reach, and they would have bounced on the next send to that group. This is why a list can bounce at 4.6% and still hold a large pool of dead addresses. A send reveals only the addresses it reaches, and verification reveals the rest.
Actions:
- Suppress the 980 invalid addresses permanently.
- Hold back the 1,540 Risky addresses. Catch-all domains accept any address, so a result there can't confirm that a mailbox exists. Check important individual Risky addresses with the free email checker, and read the catch-all email verification guidance on how to treat those results.
- Replace the redirect host in the template, then request removal from the DBL.
- Send the next campaign only to the 11,480 Valid addresses, and recheck bounces and the DBL after the send.
The cost: The Pro plan is $29 for one month, or $25 a month on annual billing, which is $300 a year. One month covers the full list and the rest of that month's deep verification allowance. For a team facing a listing that can stall a quarter's campaigns, that is a small cost. Our guide to email verification pricing compares how plans are structured.
Bottom line: The listing came from a template link, but the bounce pattern pointed to a decayed list. Fixing both is what keeps the next check clean.
How often should I check, and how do I keep it sustainable?
Check within 24 hours of any campaign that reaches more than 10% of your list, and run a scheduled DNS query at least weekly for every IP and domain you send from. The 10% threshold is our recommendation, not an industry standard. Monthly checks miss listings that appear and clear within a few weeks.
Three habits make this manageable:
- Automate the DNS query. A scheduled script that logs results and alerts on any 127.0.x.x answer takes a short time to set up. If you want to automate verification too, see our guide to email verification API and automation. Unlimited Verifier's email verification API accepts single-email checks and bulk batches of up to 10,000 emails per request, and API access is included on the Pro plan.
- Verify at the point of entry. Most listings trace back to bad addresses entering the list. Real-time email validation at signup stops many of them, and our guide to ways to avoid hitting spam traps covers the rest.
- Clean on a schedule. Lists decay as people change jobs and mailboxes close. A regular cadence, set out in our list maintenance best practices, is part of email verification compliance and hygiene. For SaaS and ecommerce teams, where B2B addresses churn quickly, email verification for ecommerce and SaaS covers the specific workflows.
If you are choosing a verifier to support this, our roundup of the best email verification tools and guide to choosing an email verifier explain what to compare.
Bottom line: A weekly scripted DNS query plus verification at entry catches most listings before they cost you a campaign.
What are the most common mistakes when checking blacklists?
Most mistakes come from checking too little, too rarely, or fixing the symptom instead of the trigger.
- Checking only the domain. A clean domain can still sit on a listed sending IP, and the reverse is also true.
- Ignoring link hosts. Tracking and redirect hosts are a frequent trigger, and a flagged subdomain can be invisible if you only check the registered domain.
- Treating every hit as an emergency. A single niche listing with no change in bounces or complaints calls for investigation, not a campaign freeze.
- Requesting removal before fixing the cause. This is the most common reason removals are refused.
- Using a public resolver for DNS queries. A 127.255.255.x response means the query was refused. It does not mean you are listed.
- Checking once a month. Short listings can start and clear between checks.
- Assuming verification removes a listing. Verification prevents future listings by reducing bounces and spam-trap hits. It does not lift an existing listing.
- Relying on a single checker. Different tools query different lists, so one clean web result is a starting point, not a full answer.
Bottom line: Check all four identifiers, check on a schedule, and fix the trigger before you ask for removal.
How we compared (and limitations)
This guide is based on public documentation: RFC 5782, Google's and Yahoo's published sender requirements, Spamhaus's and Barracuda's published list policies, and Microsoft's Sender Support documentation. We have not run controlled tests of any list's review times or removal processes. Listing durations vary by list and reason and change without notice, so your own log will be more reliable than any general figure.
Unlimited Verifier checks email addresses, including syntax, domain, MX records and the SMTP mailbox, and sorts results into Valid, Risky and Invalid. It does not replace a blocklist lookup. Its free domain blacklist checker is a convenient first look, and the DNS method above is the reliable check. Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark.
When you're ready to clean the list behind a listing, sign up for a free account and upload and verify your list. For the broader picture of how listings happen, read our spam traps and email blacklists guide.
Worked dig lookup for an IP listing
To check the IP 192.0.2.10 against Spamhaus ZEN, reverse the octets and append the list zone:
dig +short 10.2.0.192.zen.spamhaus.org
- Empty output: not listed on ZEN.
- 127.0.0.2 or similar: listed; see Spamhaus documentation for the code meaning.
- 127.255.255.254: query refused, usually from a public resolver. Re-run from your own resolver.
Repeat for each list you monitor and log the date, so you can see whether the listing appeared during your last send.
Frequently asked questions
What does a 127.0.0.x response mean from a blocklist?
A 127.0.0.0/8 answer means the IP or domain is listed on that DNSBL. The last octet often indicates the listing type, which the list's documentation explains. An empty response (NXDOMAIN) means the subject is not listed on that list.
What does 127.255.255.x from Spamhaus mean?
A 127.255.255.x response from Spamhaus means your query was refused, not that you are listed. This usually happens when you query through a public resolver or a high-volume shared DNS service. Run the lookup from your own resolver or use Spamhaus's approved access method.
Can a domain be blacklisted if its IP is clean?
Yes. Domain listings apply to the domain in your From, Return-Path, DKIM d= value, or links, so a clean sending IP can still carry a listed domain. Check each identifier separately to find which one is flagged.
How long does a blacklist listing last?
It varies by list and by cause. Some listings clear within days once the sending problem stops, while others persist longer or require a removal request. Check the specific list's policy page for its expiry rules, since timelines are list-specific.
Should I request removal immediately after a listing?
Not before you fix the cause. Removal requests are often refused when the trigger, such as a compromised account, purchased list or unsubscribe failure, is still active. Fix the problem, confirm sending is clean, then submit the request.
Are there free tools to check blacklists?
Yes. Many free web checkers query multiple DNSBLs at once and show results in one view. They are useful for quick checks, but for repeatable monitoring, a scripted dig query against each list's zone gives a consistent record you can log over time.
Does Gmail use a public blacklist I can query?
As far as public documentation shows, Gmail and Outlook.com do not publish a DNSBL you can query. Their filtering problems appear in their own dashboards, such as Google Postmaster Tools for Gmail, so check those alongside DNS lookups.
How often should I check my domain for blacklisting?
Check after every large send and run a scripted weekly check at minimum. Listings can appear and clear between monthly reviews, so a single point-in-time check can miss a short listing that affected your last campaign.
Why does my domain show as blacklisted on one checker but not another?
Checkers query different lists, and lists differ in their criteria and update timing. A listing may exist on one list today and not on another. Compare results across the lists that matter for your sending, and check each list's own status page.
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.