A DNS blocklist listing is a signal to investigate, not a reason to submit a removal request before the cause is fixed. Start by stopping the spam, abuse, compromise, or configuration problem that caused the listing. Confirm which organization owns the affected mail server or public IP, because a cloud or ISP provider may need to take the provider-facing action.
Spamhaus ZEN
ZEN combines several Spamhaus IP blocklists. Use the official Spamhaus IP and Domain Reputation Checker to look up the affected IP, understand the specific listing, and follow the returned remediation or removal path. Spamhaus directs ZEN users to that checker for listing detail and next steps.
Do not pay a third party that offers to remove a Spamhaus listing. Spamhaus states that removal is never charged and that paid removal offers are scams. If the IP is owned by an ISP, hosting provider, or cloud provider, coordinate with its abuse or security team, since it may be the party authorized to request removal.
Official references: Spamhaus ZEN blocklist and Spamhaus listing and removal FAQ.
SpamCop
Use the official SpamCop Blocking List checker to confirm the affected server. SpamCop lists IPs that have sent reported mail and describes its list as time-based: when reports stop, delisting is normally quick and automatic.
Focus on eliminating the source of reported mail and verifying that the sending IP is under the responsible owner’s control. If you received a SpamCop report, follow the links in that report for the message-specific details and response options. Avoid trying to force removal before the sending issue is resolved, because new reports can keep or return the listing.