Is my email domain blacklisted, or is it something else?#
Start with the smallest useful question: who told you? A public blacklisting is something a stranger can look up, so if a receiving server refused your mail and the bounce text names a list and gives a reference number, that is a real listing and it is evidence. If instead one person at one company stopped seeing you, or your test send landed in spam at Gmail but arrived fine elsewhere, you are describing a filter or a private block, which no public lookup will confirm or deny.
The third case is the one that generates most of the worry and almost none of the substance. People search for their own personal address, the one on Gmail or Outlook, and expect a list to say yes or no. There is no such list. A free mailbox address is not independently listed; the block that can affect it is either the whole provider being unhappy with the server that sent it, or a recipient having blocked you on their own account. Neither is visible to you.
What are the three kinds of blacklisting, and which one is mine?#
The distinction is worth making once and keeping, because a person who understands it stops wasting checks on the wrong object.
| What is listed | Who maintains it | Can you look it up | Who clears it |
|---|---|---|---|
| A server IP address | A blocklist operator, published for any mail server to query | Yes, free, by IP or by range | The company that owns that address block |
| A domain name | The same operators, in a separate domain list | Yes, free, by domain | Usually the domain owner, through the operator's own form |
| A single address in one mailbox | That one reader, in their own settings | No. Not published, not visible to you | Only that reader, by unblocking you |
| A sender reputation score | A mailbox provider such as Google or Microsoft, about you | Only in their own sender console, after you prove the domain | Nobody clears it. Time and clean sends do |
The first two are the classic lists, and operators describe them as DNS-based blacklists, also called real-time blacklists, DNSBLs or RBLs. The last two are not lists you can check in a scanner at all, which is why an anxious person can run six lookups, get six clean results, and still have mail arriving in spam.
How do I check if an email domain is blacklisted?#
Four things get looked up when a filter decides whether to accept your message, and a check on only one of them proves nothing about the other three. Run the check on all of them.
- The domain in the From line, because a blocklist consulted at that stage is judging the name the reader sees.
- Any other domain you link to in the message, including a link shortener, because filters also look up the addresses hosting what is inside the email.
- The IP address that opened the connection to the receiving server, which is often not yours.
- The reverse DNS name of that IP, and whether it matches what the server announced about itself.
Then pick your checker according to what you have. A domain name goes to the blocklist operator's own lookup. An IP goes to a multi-list checker, because a single operator tells you about a single list, and the value of a broad scan is breadth rather than authority. MXToolbox, one of the older scan pages, describes its own blacklist check as testing a mail server IP against over 100 DNS-based email blacklists in one pass.
The step almost everyone skips is the second one. If your newsletter links to your own website, and that website domain is listed, your mail is judged on it even though you never mailed anything from that name. Operators are explicit that a domain list covers domains appearing in headers and content, and that listings record the hostname rather than a full page path.
Which IP do I look up when I send through someone else's server?#
Look up the address that delivered the mail, not the address of the computer you typed the email on. If you send through a marketing platform, an SMTP relay or a mailbox provider, the connecting IP belongs to them and your home or office connection is irrelevant to the question.
Two easy ways to find the real one. A bounce from a receiving server normally quotes the address it rejected, and a support page that says your IP is listed will quote the number. Or read the Received lines at the bottom of the header of a message you sent yourself, where the last one before the destination is the server that handed it over. A checker can also do this for you: MXToolbox suggests starting with a mail exchanger lookup on your domain, or sending a message to its own test address and letting the arrival tell you where it came from.
How do I check for a listing at the big blocklist operators?#
Each operator publishes its own free lookup, and each lookup is the only place its own listings are guaranteed to be visible. Spamhaus sends anyone who believes a domain of theirs is listed to its combined IP and domain reputation checker, which returns the reason and the removal steps for its own zones. Microsoft's sender console for Outlook.com shows status for the addresses you ask to be responsible for. SpamCop, which began as a place to report spam rather than a place to check, publishes a blocking list of its own and a page for senders who have been reported.
A practical order: run one broad multi-list scan to find out whether anything anywhere is unhappy, then go to the specific operator named in the bounce and read their own entry, because that is the one whose removal steps you are about to follow.
One limit worth knowing. These lists are published for mail servers to query. Reading them by hand through a free web page is a different thing from pointing your own infrastructure at them, and the free tiers of that second activity come with terms attached. Nothing stops you checking your own domain ten times in an afternoon.
What does a rejection message that names a blocklist mean?#
It is the best evidence you will get, and it arrives as a bounce with a code and a sentence. The useful part is the reference: a ticket number, a listing code, or a link to a page that explains the listing. Keep that text. A removal request that quotes the rejection you were handed is answered differently from one that says only that mail to that company is failing.
Sort the rejection before assuming it is a listing at all. A permanent refusal for an address that no longer exists is a hard bounce and has nothing to do with reputation. A temporary refusal, often a message about volume or rate, is a throttle, and it clears by slowing down rather than by asking to be delisted. Why your email is not sending walks through the two readings, and the difference matters here because a throttle is often the sound of a listing being applied on the fly rather than a published entry.
Why would a domain be listed at all?#
Operators do not publish the exact rule that fired. Spamhaus is blunt about this on its own domain list page: several criteria must match, the specific ones are not discussed in most cases, and listings are re-evaluated constantly. What they do publish is a set of observations about what degrades a name, and those are worth reading as design advice rather than as a checklist.
- A brand new name has no history, and one operator states plainly that an unknown reputation begins as poor by default, because an unfamiliar domain is a much higher risk of emitting spam than a known-good one.
- Rotating between many domains and many addresses is a pattern associated with spammers, and names that behave that way are treated accordingly. Long-lived infrastructure is the defence.
- Authentication records are necessary but not protective. SPF, DKIM and DMARC can be set up by a bad sender as easily as a good one, and listings happen to domains with and without them.
- Mail to addresses nobody confirmed. The same operator recommends double opt-in as a way to avoid spam traps rather than as a courtesy.
- No abuse address and no feedback loop, which the operator describes as a domain's own abuse detection system. Without them you learn about a problem from a bounce instead of from a report.
- Hosting, nameservers or website DNS sitting on infrastructure that tolerates abuse, which drags the reputation of everything on it.
Does being blacklisted mean I did something wrong?#
No, and this is worth saying in the middle of a bad afternoon. One of the major IP lists defines spam as unsolicited bulk email and states explicitly that it does not evaluate the content or the legality of a message, only whether it fits that definition. Another of the same publisher's lists is described as holding addresses that are not bad in themselves but should never be sending mail directly, because they are end-user ranges meant to submit through an authenticated server.
So a listing is an observation by one system, made at one moment, from signals that operator will not fully explain. It is not a verdict about your conduct, and a single entry does not mean the whole internet has refused you. Where a list is consequential is in the mail filters that consult it, and plenty of receiving systems consult none of them.
How do I get my domain off a blocklist?#
Ask on the operator's own page, after fixing whatever produced the listing. The order is not politeness. A request submitted while the cause is still running gets approved, then the domain gets re-listed by the same automated system within a day or two, and a pattern of re-listings is a worse signal than a first one.
Who is allowed to ask changes by list type, and it is the part people get wrong most often.
| The listing | Who can request removal | What the operator says about it |
|---|---|---|
| A domain name list | The domain owner, through the operator's checker | Most entries expire by themselves once the triggering activity stops. Using the form does not guarantee removal. |
| An IP reputation list | Nobody except the network or hosting company that owns the address | Notifications go to that company, general users are told to speak with their provider, and the owner is responsible for asking when the cause is gone. |
| A policy list of end-user ranges | The address owner, but not from a free webmail account | Requests sent from a free email domain are not processed, and removals made that way are automatically reversed. |
| Status inside a mailbox provider | The sender, in that provider's own console | Outlook's sender service gives you data about addresses you are responsible for, and reputation is described as always the sender's job. |
| One reader's blocked sender list | That reader alone | Blocking sends future mail from you to their spam folder; unblocking sends it back to their inbox. |
The practical shape for a small sender: if your domain is on a domain list, that is your own errand and you can do it today. If a server address is on an IP list, you almost certainly do not own that address, so the errand belongs to whoever does, and your move is to open a ticket with them and quote the rejection text.
How long does a delisting take to work?#
Short answer, from the operator: once a removal request is approved it is processed immediately, and it should take only minutes. The honest addendum is that some systems reading the list may lag up to a full day before they stop seeing the entry, and an entry still present a day after approval is worth chasing back to the operator.
Two things that do not follow from that. First, delisting is not the same as recovery, because the reputation the listing damaged is a separate object with a longer memory. Second, a cleared listing can return without anyone doing anything new, since automated lists re-detect. If your volume is going to a mailbox provider that watches complaint rates, sender reputation is the slower clock you are working against.
Can I pay a service to get me delisted?#
Do not, and the reason is published by the operator rather than by a blogger. Spamhaus states that there is never a charge or fee for removing any of its listings, that any offer from anyone to remove a listing for money is a scam, and that it has no affiliation with anybody selling blocklist removal and no third party can influence or speed up a removal.
What a paid service can legitimately sell is the labour around the problem: reading the rejections, finding which of your four looked-up objects is listed, and writing the request. That is a real service. It is also a twenty-minute job that the free pages above already describe, and nobody can buy you an approval.
What if it is my email tool's address that is listed, not mine?#
This is the commonest dead end for a small sender, and the map is simple. The IP that opens the connection is usually the platform's or the mail service's, so an IP listing is an errand for that operator, and your route is support plus the rejection text. Your verified sending domain, by contrast, is yours, so a domain listing is your errand even if you mail through a tool.
There is a shared-infrastructure consequence to accept as well. On a shared address, one careless sender on the same pool can make your mail slower to arrive, and no setting on your side fixes that. This is one of the two real arguments for sending from a domain you own and, later, an address you alone use; the other is that your history stops being somebody else's.
Is there a Google blacklist I can check myself against?#
Not in the sense most searches mean. Google publishes sender requirements rather than a public list you can look your name up on, and its own framing is that the requirements help ensure delivery and prevent Gmail from limiting sending rates, blocking messages, or marking them as spam. Since February 2024 the baseline for everyone mailing Gmail accounts is SPF or DKIM on the sending domain, valid forward and reverse DNS records, an encrypted connection, messages built to the internet mail format, and no impersonation of Gmail addresses in the From line. Above five thousand messages a day to Gmail, the same page adds both SPF and DKIM plus a DMARC policy.
Google also states the one number it will commit to: keep the spam rate reported in its Postmaster console below 0.3 percent. That console is the closest thing to a self-check, and it is not a blacklist, since it shows how your own verified domain is doing rather than whether you appear on a list.
On the receiving side, a reader can block your address in their own Gmail settings, and Google says plainly what happens: all future mail from you goes to their spam folder, and unblocking sends it back to their inbox. That is why one person's complaint is a bad sign about your list rather than evidence of a listing.
How is a Microsoft block different?#
Outlook.com publishes sender data instead of a public list. Its Smart Network Data Services page says deliverability there is based on your reputation, that you log in with a Microsoft account and request access to the addresses you are responsible for, and that reputation remains the sender's own responsibility. The same console carries the junk mail reporting programme, so you receive copies of complaints about your own mail, and Microsoft notes it is also a way to spot a compromised server, malware or a botnet on your own network.
Two practical notes on that console. Access to a network is not permanent; Microsoft states it expires ten months after approval or migration unless ownership is re-attested, so an old account can quietly stop showing you anything. And the whole thing is scoped to addresses you are responsible for, which is a real limitation if your mail leaves through a shared pool you do not control.
Can a link inside my email get my domain listed?#
Yes, and this is the listing that surprises people most, because it happens without you sending anything from the domain in question. Filters consult domain lists against names in the message as well as the sender, so a link to a compromised website, an old landing page on an expired domain, or a redirect service with a bad neighbour can all be judged as part of your mail. Listings record the hostname rather than a full page path, which means a single bad section can carry the whole name.
The check takes five minutes: read your last three campaigns and look up every domain you linked to, including the ones you stopped maintaining. If you find a listing on a name you no longer use, delete the link rather than chasing the delisting.
How do I stop getting listed again?#
- Fix the cause before asking for removal, because an approved delisting over an active problem comes straight back and a re-listing is harder to argue with than a first one.
- Send only to people who confirmed. This is the single intervention that touches complaints, traps and reputation together, and it is how double opt-in works in practice.
- Keep one stable domain and stop rotating between names, because the pattern of frequent change is itself treated as a signal.
- Run authentication properly on the domain you mail from, then confirm it is passing rather than merely published. SPF, DKIM and DMARC explained covers what each one proves.
- Put a working abuse address on the domain and read it, since a report that reaches you is information and a report that bounces is a listing waiting to happen.
- Prune the list on a schedule so that a dead address is discovered by your own cleaning pass rather than by a spam trap. How to clean an email list sets out the passes and how often each is worth doing.
What should I check first if mail fails at only one company?#
Not a blacklist scanner. A failure at one recipient, at one company, on one day is usually about how that company judges that message or that sender right then, which is a different object from a published listing. Read the bounce for a code and a sentence, compare against what your own report says happened, and check whether the volume jumped. If the pattern is one company only, why email goes to spam is the more useful page, and it separates the sender problem from the content problem.
Most listings that reach a small sender are avoided by three habits that a tool can enforce for you: mail from a domain you own and have verified, hold unconfirmed addresses out of every send until they click, and let an address that bounces or complaints drop out of the next campaign on its own. Campaign Kicker does those three, shows the bounces and complaints per send, and ramps volume on a new domain instead of releasing it all at once.
Start free, no card