Mail server address is listed on a blocklist
What this check looks for
One of your mail server addresses appears on ‹list name›. Receivers that consult that list will reject or quarantine mail from this address until it is removed.
Why it matters
A blocklisted sending address is the single fastest way to lose email delivery entirely, and the effect is immediate. Removal is usually free and self-service, but the listing returns unless the cause is fixed first.
When the check passes, your report says: “Mail server addresses are clear on every list we checked”.
What it costs your score
When this check fails it removes 40 points from your Email reputation score, before the status, confidence and repeat multipliers are applied. Email reputation carries a weight of 5 in the overall score.
It shares the email-reputation.blocklists family ceiling of 80 points: however many findings that family produces, together they cannot remove more than that from Email reputation. One underlying problem showing up in several places is still one problem.
- Severity
- critical
- Default confidence
- confirmed
- Status when triggered
- fail
- Deduction
- 40 points
- Family cap
- email-reputation.blocklists · 80
- Category
- Email reputation
- Module
- Email blocklists
- Fix owned by
- user
- In the ruleset since
- 2026.09
How to fix it
Find and fix the cause, then request delisting at ‹delisting url›.
Delisting before the cause is fixed produces a relisting within days, often with a longer cooling-off period.
Find the cause first. The usual four are: a compromised mailbox or web script sending spam; an open relay; a mailing list sending to addresses that never opted in; and a shared address whose neighbour is the actual sender.
Check your mail queue and outbound logs for volume you did not send. On a shared or cloud host, check whether the address is yours alone.
Fix what you find — rotate the compromised credentials, patch or remove the script, close the relay.
Then request removal at ‹delisting url›. Most lists remove within hours once the cause has stopped.
Confirm the supporting configuration is right so it does not recur: reverse DNS for the address, an SPF record that does not authorise more than it should, and DMARC at enforcement.
How to confirm it worked
Re-run this check after requesting removal; the listing should be gone.
Send a test message to a mailbox at a large provider and confirm it reaches the inbox.
A named slot like ‹domain› — and the braces left in the configuration below — is filled in with your own values when this rule appears on a report.
Technical detail
‹address› is listed on ‹list name›. Reason given: ‹listing reason›. ‹listing text› A DNSBL answers a query for a listed address with a 127.0.0.0/8 code and answers NXDOMAIN for an unlisted one (RFC 5782 §2.1); this finding rests on a code we received, not on the absence of one. ‹list caveat›
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.