Root cause
Why are my emails going to spam? — full fix guide
A blocklist hit is one of a dozen reasons mail lands in spam. This guide covers the rest.
Read moreFree tool · No account
A single blocklist hit can quietly tank your inbox rate at the providers that respect it. Check your sending IP or domain against every major DNSBL at once, with a direct link to request removal from any that flag you.
Enter a domain or a sending IP address. We resolve domains to their A record automatically, then check against 6 major DNS-based blocklists in parallel.
How this works
Each blocklist publishes a DNS zone. To check an IP, you reverse its octets and query "<reversed-ip>.<zone>" for an A record — if one comes back, the IP is listed. It's the same mechanism every major mail server uses internally, just exposed here as a simple form.
Fix the underlying cause first — usually a spam trap hit, a compromised account sending abuse, or a shared IP poisoned by another tenant — then use the removal link for that specific blocklist. Requesting removal before fixing the cause just gets you re-listed.
DNSBLs are one signal among many. Gmail, Outlook and Yahoo weigh engagement, content, authentication, and their own private reputation systems far more heavily than public blocklists for everyday filtering decisions — a clean check here doesn't guarantee inbox placement.
Spamhaus and SpamCop are the two most widely respected across mailbox providers and spam filters. Barracuda and Mailspike matter mainly for recipients running that vendor's own security appliance. UCEPROTECT and SORBS are more aggressive and have higher false-positive rates — a listing there is worth investigating but less urgent.
Blocklists are one signal of many
Brain combines blocklist status with Google Postmaster, Microsoft SNDS, and Sender Score data into one reputation score — and traces every drop back to a root cause automatically.