SORBS was officially decommissioned in June 2024. It no longer accepts spam reports, publishes active blocklist data, or processes delisting requests—so any “SORBS listing” you see today is a legacy reference and should be removed from filtering configurations.
To check whether your domain or IP is currently flagged on active blocklists, use InboxAlly’s free Spam Database Lookup. For ongoing monitoring, use Domain Reports in the InboxAlly app.
What is SORBS?
SORBS (Spam and Open Relay Blocking System) was a DNS-based blocklist (DNSBL) that historically listed IPs/domains suspected of sending spam or operating insecure mail infrastructure (like open relays).
As of June 2024, SORBS is offline and no longer maintained, so it should not be relied on for modern filtering decisions.
Why am I listed on SORBS?
If you’re seeing references to a SORBS “listing,” it’s typically due to one of these situations:
- Outdated documentation or tooling still checking SORBS zones
- Legacy logs from older deliverability incidents
- Mail server or gateway configurations that still reference SORBS for blocking decisions
Historically (before decommissioning), SORBS used signals such as:
- Spam traps (addresses used to identify unsolicited mail)
- User complaints and direct reports received by administrators
- Behavioral patterns associated with bulk spam activity
- Dynamic IP ranges (often flagged to discourage running mail servers on consumer/residential connections)
How to get removed from SORBS
You can’t. Since SORBS is decommissioned, there is no active delisting process and no authoritative listing data to remove.
What you should do instead:
-
Remove SORBS from any filtering or monitoring configuration
- Check mail gateways, anti-spam appliances, and any custom DNSBL checks.
-
Verify your real blocklist status on active lists
- Run a scan with InboxAlly’s free Spam Database Lookup.
-
Set up ongoing monitoring
- Use Domain Reports in the InboxAlly app to track reputation and authentication signals over time.
How does this affect deliverability?
A SORBS “listing” should have minimal to no impact on deliverability today because the service is decommissioned and no longer provides active data.
However, deliverability problems can still happen if:
- A receiving system is misconfigured and still attempts to use SORBS (this can cause false blocks or lookup failures).
- You’re listed on other active blocklists (which can directly affect acceptance, throttling, or spam placement).
If you’re troubleshooting delivery issues, start by confirming your current status with the Spam Database Lookup, then address any active listings and underlying causes (list hygiene, authentication, complaint rates, sending patterns).
Frequently Asked Questions
What was the purpose of the SORBS spam list?
SORBS aimed to reduce spam and abuse by listing sources associated with spam sending, open relays, compromised systems, and other risky email infrastructure.
What happened to the SORBS spam blocklist?
It was officially decommissioned in June 2024. SORBS is no longer maintained, and its reporting, lookup, and delisting functions are shut down.
Can I do a SORBS blacklist check?
Not in a meaningful, current way—SORBS is decommissioned. Instead, check your domain/IP against active blocklists using InboxAlly’s Spam Database Lookup.
How did SORBS collect spam data (historically)?
Before shutdown, SORBS relied on spam traps, user/admin complaints, and analysis of sending/network behavior patterns.
Why did SORBS target dynamically allocated IP addresses?
Dynamic/residential IPs are more likely to be associated with compromised devices and are generally not intended for running mail servers. SORBS historically listed many of these ranges to reduce abuse.
For a step-by-step process to assess impact and fix active listings, see Blocklist Impact and Remediation.