Abusix Combined Blocklist

The Abusix Combined Blocklist merges IP lists into one for faster filtering of malicious email. Use Suped to monitor blocklist or blacklist status.
Updated on 17 Jun 2026: We added clearer guidance on finding the listed sending IP and checking the Abusix delisting path before chasing broader delivery issues.
Summarize with
Check if you are listed on Abusix Combined Blocklist
And 143 other blocklists.















What is Abusix Combined Blocklist?
The Abusix Combined Blocklist is a real-time IP-based blacklist (or blocklist) used by mail servers to filter inbound SMTP traffic. It aggregates Abusix's IP, exploit, and policy lists into one DNSBL/RBL query, so administrators can check one zone instead of querying those zones separately. The list covers IPv4 and IPv6 addresses and is designed for mail systems that can query DNS reputation lists during SMTP processing.
Mail servers query this blocklist using the DNS zone combined.mail.abusix.zone. A positive match returns a 127.0.0.x response code, and the receiving server can reject or score the message based on its local policy. The code points to the source list behind the match, but the Abusix lookup result or rejection message usually gives the clearest reason for the listing. Response codes for this blacklist can include:
- 127.0.0.2
- 127.0.0.3
- 127.0.0.4
- 127.0.0.11
- 127.0.0.12
- 127.0.0.200
Who runs Abusix Combined Blocklist?
Abusix runs the Combined Blocklist as part of its email and network abuse data. The company works with mail operators, Internet service providers, telecommunications companies, hosting providers, and cloud providers that need to detect spam, phishing, malware, compromised hosts, policy-listed IP ranges, and other abusive SMTP traffic.
How to identify the listed IP
If a rejection is caused by this blacklist, the bounce message usually names Abusix, includes the connecting mail server IP, and can show the zone combined.mail.abusix.zone. The IP in that SMTP rejection is the IP to investigate. For most senders, that is the outbound mail server or email provider IP, not the public IP shown by a browser search.
Example bounce message
554 5.7.1 Service unavailable; Client host [192.0.2.128] blocked using combined.mail.abusix.zone
If messages land in spam without a clear SMTP rejection, treat it as a broader filtering or IP reputation problem first. Delisting an IP from Abusix only fixes delivery failures where the receiving system is actually using the Abusix blocklist or blacklist data.
How do I get removed and delisted from Abusix Combined Blocklist?
Before requesting removal from this blacklist, identify and fix the root cause of the listing. Listings on the Abusix Combined Blocklist are evidence-based and usually come from recent spam trap, honeypot, heuristic, or policy signals tied to the sending IP. The most common reasons include:
- Sending spam to spam traps or honeypots.
- Compromised user accounts, devices, websites, or mail servers sending spam, phishing, or malware.
- Poor list hygiene, including purchased lists, appended email data, missing confirmed opt-in, or weak anti-bot protection on signup forms.
- Sending to very old email addresses with no recent engagement, especially addresses with no interaction for more than two years.
- Missing or broken bounce and engagement management processes.
Once you have resolved the underlying issue, request delisting through Abusix's Lookup and Delisting page. Abusix requires a free account for delisting because anonymous removals were abused. Enter the listed IP address, review the listed reason, create or confirm your account, and follow the portal instructions. Delisting requests are processed immediately; Abusix says DNS zone files are rebuilt every minute, so the change usually appears within five minutes. If a local mirror or cached resolver is involved, some systems take longer.
Abusix also says listings usually expire about 5.2 days after the last bad event, but waiting for expiry does not fix the sending problem. If the same behavior continues, the IP can be listed again after removal.
What's the impact of being listed on Abusix Combined Blocklist?
The impact of being on the Abusix Combined Blocklist is usually medium. It is not used by every mailbox provider, but mail systems that query the combined DNSBL can reject messages during SMTP, causing visible bounce messages and failed delivery to those recipients. A listing also signals an IP reputation problem that can overlap with spam complaints, malware cleanup, compromised account response, and sender authentication checks.
Suped's product can monitor blocklist or blacklist status for sending IPs, keep the delisting workflow tied to DMARC, SPF, and DKIM checks, and show when an incident has cleared across monitored sources.
Other Abusix blocklists
Abusix Authbl Blocklist
Organization
Abusix
Zone
authbl.mail.abusix.zone
Type
IP
Impact
Medium
Delisting
Manual
Abusix Domain Blocklist
Organization
Abusix
Zone
dblack.mail.abusix.zone
Type
Domain or IP
Impact
Medium
Delisting
Manual
Abusix Exploit Blocklist
Organization
Abusix
Zone
exploit.mail.abusix.zone
Type
IP
Impact
Medium
Delisting
Manual
Abusix nod List (Newly Observed Domains)
Organization
Abusix
Zone
nod.mail.abusix.zone
Type
Domain
Impact
Medium
Delisting
Automatic
Abusix noip List (Newly Observed IPs)
Organization
Abusix
Zone
noip.mail.abusix.zone
Type
IP
Impact
Medium
Delisting
Automatic
Abusix Policy Blocklist
Organization
Abusix
Zone
dynamic.mail.abusix.zone
Type
IP
Impact
Medium
Delisting
Manual
Abusix Spam Blocklist
Organization
Abusix
Zone
black.mail.abusix.zone
Type
IP
Impact
Medium
Delisting
Manual
