Definition
Blocklist: A list of IP addresses or domains associated with spam or abuse that receiving servers query in real time. A DNS-based blocklist (DNSBL, RFC 5782) is checked by reversing the IP octets and looking them up under the list zone; an answer such as 127.0.0.2 means the address is listed.
How DNS blocklists work
Most blocklists are published over DNS so that a lookup takes milliseconds. To check 192.0.2.10, a receiving server reverses the octets and queries 10.2.0.192 under the list zone. An answer in the 127.0.0.x range means listed, and no answer means clean.
Domain blocklists work the same way but take a domain name instead of an IP. Receivers use them to judge the domains in your From address, your links and your envelope sender.
Why senders get blocklisted
The usual trigger is mail to spam traps, which only happens when a list contains addresses nobody signed up with. Old segments, purchased lists and scraped contacts are the classic sources.
Other triggers are high complaint rates, a sudden jump in volume from a new IP, and compromised accounts or web forms sending spam on your behalf. On shared IPs you can also be listed because of another sender on the same address.
How to get off a blocklist
Find and fix the cause first: stop mailing the segment that hit the traps, close the abused form, secure the account. Then use the operator's own lookup page to request removal, explaining what you changed.
Many listings expire on their own once the bad traffic stops. Requesting removal without fixing the cause usually gets you listed again within days.
$ dig +short 10.2.0.192.bl.example.org A
127.0.0.2
$ dig +short 10.2.0.192.bl.example.org TXT
"Listed for spam trap hits, see https://bl.example.org/lookup?ip=192.0.2.10"How RocketVerifier handles it
Our free blacklist checker tests a domain or IP against the major DNS blocklists in one pass, and Monitors repeat SPF, DKIM, DMARC and blocklist checks on a schedule with alerts when something changes. Our own verification IPs only carry traffic while their blocklist checks stay clean and step back automatically if one is listed. When a receiving server rejects a probe because of a listing or another policy, the address is reported as blocked (unknown), never as undeliverable, and is not charged.