GBUdb's "truncate" list contains only IP addresses its statistical network is highly confident are pure spam sources. It is designed for very low false positives and entries expire automatically once the bad behaviour stops.
Why an IP gets listed on GBUdb Truncate
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 has moderate adoption; a listing may affect some receivers but rarely causes a broad delivery failure on its own.
How to delist from GBUdb Truncate
GBUdb Truncate 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 GBUdb Truncate?
Enter your mail server's IP address (or your domain) in the checker above. It queries GBUdb Truncate 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 GBUdb Truncate?
GBUdb Truncate 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 GBUdb Truncate listing stop my email being delivered?
It has moderate adoption; a listing may affect some receivers but rarely causes a broad delivery failure on its own.