SpamRATS RATS Spam Blacklist

SpamRATS is an IP-based blocklist (blacklist) identifying addresses sending high volumes of spam from compromised servers or spam-optimized hosts.
Updated on 17 Jun 2026: We updated this guide to clarify RATS-Spam lookups, delisting prerequisites, and how SPF, DKIM, and DMARC fit into IP reputation investigations.
Summarize with
Check if you are listed on SpamRATS RATS Spam Blacklist
And 143 other blocklists.















What is the SpamRATS RATS-Spam blacklist?
The SpamRATS RATS-Spam blacklist is an IP-based real-time blocklist (blacklist) and DNSBL/RBL that lists IP addresses repeatedly observed or reported sending high volumes of spam. SpamRATS says the list includes IPs tied to compromised servers, hosts or relays, and mail servers set up to send unsolicited email. SpamRATS also says this activity accounts for about 30% of wasted mail server overhead.
SpamRATS says an IP address is added only after a significant amount of spam-style behavior has been observed or reported, which is intended to keep false positives low. Because this blacklist is narrow, administrators usually use it as one signal in a wider anti-spam policy instead of as the only reason to reject a message.
Who runs SpamRATS RATS-Spam?
SpamRATS is operated by mThreat Technology Inc., which identifies SpamRATS as a registered trademark. SpamRATS provides IP reputation data and Real-Time Blackhole List (RBL) services for network and email administrators.
SpamRATS says its IP reputation data has been used in production environments for over 15 years. It maintains several IP reputation blocklists for different threat patterns, including spam sources, dynamic-looking hosts, missing reverse DNS, and authenticated-abuse signals.
How is SpamRATS RATS-Spam queried?
SpamRATS RATS-Spam can be queried like a DNSBL/RBL. The official hostname uses an API key before the spam zone, so operators need a SpamRATS API key before adding the list to mail server policy.
RATS-Spam query hostnametext
[YOUR_API_KEY].spam.spamrats.com
This is for inbound filtering, not sender authentication. A RATS-Spam lookup checks the connecting IP reputation; SPF, DKIM, and DMARC tell receivers whether a domain authenticated a message and what policy to apply. Suped's product helps teams monitor DMARC reports and DNS records while they investigate whether an IP listing came from compromised mail flow, an unauthorized sender, or a broken authentication setup.
How do I get removed and delisted from SpamRATS RATS-Spam?
SpamRATS provides a self-service removal process for RATS-Spam. Before requesting delisting, fix the spam source that caused the listing, such as a compromised mailbox, infected host, open relay, abused script, misrouted application mail, or unauthorized sender using your infrastructure. SpamRATS warns that continued abusive behavior after removal can make future removals harder.
If you are not the email administrator and do not own or manage the mail server, SpamRATS says you should contact your ISP or help desk instead of trying to remove the IP yourself. For mail client issues, they point users toward authenticated submission on port 587.
Once you have addressed the cause of the listing:
- Check the IP on the SpamRATS removal page to confirm whether it is listed and start the delisting flow.
- If automatic removal is not available, use SpamRATS' contact form and include the affected IP plus the specific fix applied on the sending system.
What's the impact of being listed on SpamRATS RATS-Spam?
A SpamRATS RATS-Spam listing usually has narrower impact than a listing on a blocklist used directly by large consumer mailbox providers. Gmail and Microsoft mailbox filtering does not publicly name SpamRATS as a primary filtering input, but smaller ISPs, companies, hosting providers, and self-managed mail servers use DNSBLs/RBLs in connection-time filtering.
That means a RATS-Spam blacklist listing can still create bounced messages, SMTP rejections, delayed delivery, or messages routed to spam folders for recipients behind those systems. Treat the listing as evidence of a sending-IP problem, then confirm your logs, traffic volume, authentication results, and application mail sources before requesting delisting.
Other SpamRATS blocklists
SpamRATS RATS Auth Blacklist
Organization
SpamRATS
Zone
auth.spamrats.com
Type
IP
Impact
Low
Delisting
Manual
SpamRATS RATS Dyna Blacklist
Organization
SpamRATS
Zone
dyna.spamrats.com
Type
IP
Impact
Low
Delisting
Manual
SpamRATS RATS NoPtr Blacklist
Organization
SpamRATS
Zone
noptr.spamrats.com
Type
IP
Impact
Low
Delisting
Manual
