Mailspike publishes sender-IP reputation gathered from a large global sensor network and is consumed by SpamAssassin and many mail filters. Its blocklist marks IPs with a bad reputation, while a separate score grades everyone else from good to poor.
Why an IP gets listed on Mailspike
Blocklists add an IP when they see evidence of spam or abuse from it: mail hitting spam traps, a compromised server sending on behalf of a botnet, an open relay or proxy, or a sudden spike in unsolicited mail. Shared hosting and cloud IPs can also inherit a bad reputation from a previous tenant. It is used by a substantial number of mail servers, so a listing can measurably reduce delivery to those systems.
How to delist from Mailspike
Mailspike expires listings automatically once the spam stops, so the priority is to find and fix the source, a compromised account, a misconfigured server or a bad mailing. Most senders then clear within a day or two; a manual removal request can also help:
Delisting only sticks if the root cause is fixed first. Run the full Mail Health Report to catch the SPF, DKIM, DMARC or reverse-DNS problems that often cause listings.
Frequently asked questions
How do I check if my IP is on Mailspike?
Enter your mail server's IP address (or your domain) in the checker above. It queries Mailspike live and tells you immediately whether the IP is listed, along with how many other blocklists list it.
How long does it take to get delisted from Mailspike?
Mailspike removes entries automatically after a spam-free period - usually a day or two - once the source of the problem is fixed. A manual removal request can sometimes speed this up.
Will a Mailspike listing stop my email being delivered?
It is used by a substantial number of mail servers, so a listing can measurably reduce delivery to those systems.