You are on a blocklist. Now what?

Mail is bouncing, a customer forwarded you a rejection notice, or a lookup tool just showed your sending address on a list. First: this is recoverable, usually within days, and it happens to legitimate senders constantly. Second: the order of operations matters more than speed. Delisting before fixing the cause gets you relisted with a longer memory.

Step one: establish what is actually listed

A "blocklist" listing names either an IP address or a domain, and the difference decides whose problem it is. If the listed thing is your email provider's shared sending address, the fix is largely theirs (and the listing may affect thousands of their customers, which also means they are motivated). If it is your own server's address or your domain, it is yours. Check the bounce message — the rejecting server usually names the list it consulted — and then check the list's own lookup page rather than an aggregator: aggregators display stale results and lists you have never heard of.

Step two: fix the cause before touching the delisting form

Listings have reasons: a compromised mailbox spraying spam through your server, a web contact form abused as a relay, a newsletter list full of dead addresses hitting spam traps, malware on a machine inside your network, or simply a fresh IP with no history sending a large burst. Find yours before requesting removal — the serious lists check whether the behavior stopped, and a delisting followed by a relisting is scored against you. Rotate the compromised credentials, patch the form, clean the list, then move on.

Step three: delist, per each list's own process

Every list runs its own removal process, ranging from automatic expiry through self-service forms to manual review. Some well-known lists expire listings on their own once the traffic stops — for those, patience after the fix is the whole procedure. Others want a request and respond within hours to days. Never pay for delisting: the lists that matter do not charge, and services selling "express removal" are reselling free forms. And know that not every list deserves your attention — some tiny lists block half the internet and are consulted by nobody; chasing them is wasted effort.

The part that prevents the next one

Most teams discover listings from customers, days in. The fix for that is monitoring: your sending addresses checked against the lists that matter on a schedule, with severity weighted by each list's real-world impact — a major policy list is an emergency, an obscure hobby list is a note. Sojka checks your senders against tiered public blocklists every six hours (hourly while anything is listed), pushes the moment a listing appears, and carries the delisting guidance per list. You hear it before your customers do, which converts a reputation event into a maintenance task.

Check your domain free — it reads your public DNS and grades what is there.