Blacklists (DNSBL): Why Your IP Gets Listed and How to Get Off
2026-09-02 · 6 min
Every email you send is checked against several public blocklists before it reaches an inbox. If your sending IP appears on one of the major ones, your message can be silently quarantined or bounced - often with no visible error on your side. For anything that sends mail (a company server, a self-hosted box, a VPS), knowing your blocklist status is basic hygiene.
The good news: the mechanism is simple, checking it takes seconds, and getting delisted is usually quick once you understand why you were listed in the first place.
1995
The first RBL
Paul Vixie and the Mail Abuse Prevention System launch the Real-time Blackhole List, the first widely used spam blocklist - already distributed through DNS, which made it trivially cheap to query.
1998
Spamhaus appears
The Spamhaus Project launches in the UK and grows into the most operationally influential blocklist: its zones (today the combined ZEN) are checked by a majority of the world's mail servers.
2000s
An ecosystem of dozens
Barracuda, SpamCop, SORBS, UCEPROTECT and many others launch their own zones, each with its own listing policy and delisting process - checking just one list is never the whole picture.
2010
RFC 5782 standardizes it
The DNSBL mechanism itself - reversed-octet DNS queries, 127.0.0.0/8 result codes - is documented as an IETF standard, which is how every checking tool queries every list today.
How a DNSBL works (it is just DNS)
A blocklist is an ordinary DNS zone. To check an address, you reverse its four octets and prepend them to the list's zone: checking 1.2.3.4 against zen.spamhaus.org is a DNS query for 4.3.2.1.zen.spamhaus.org. If the name resolves, the IP is listed - and the returned address (always inside 127.0.0.0/8) encodes the reason, such as Spam or hijacked space.
That is the whole trick: no special protocol, no API key. It is why a checker can query seven lists in parallel with ordinary DNS and why results come back in milliseconds. The same trick powers the 'check failed' state you sometimes see - one list not answering is that list's own DNS having a bad day, not your IP being clean or dirty.
A DNSBL query is an ordinary DNS lookup of the reversed IP inside the blocklist's zone; a resolved name means listed, NXDOMAIN means clean.
Why clean IPs get listed anyway
The most common story: you rent a VPS or get a new broadband address, and it is already listed - not because of anything you did, but because the previous tenant sent spam from it. IP reputation attaches to the address, not the person. Shared hosting is similar: one misbehaving neighbour on a shared address drags everyone's reputation down.
The second story is the compromised server: an unpatched web form or a weak password turns your machine into a spam relay for a few days, and the listings arrive within hours. This is why blocklist checks are useful as an early warning, not just a post-incident chore - a sudden new listing is often the first visible symptom of a compromise.
Getting delisted (and staying off)
Every list runs its own delisting process - Spamhaus uses a web form and typically responds within hours to a well-founded request, while automated lists like UCEPROTECT delist on a timer that you cannot rush. What is universal: the listing page tells you the reason, and delisting without fixing that reason guarantees you are back within days.
Before requesting removal, close the hole: make sure no open relay or compromised script is sending mail, verify SPF/DKIM/DMARC so your legitimate mail is authenticated, and confirm the volume you send looks like a mail server, not a spam run. Then request delisting from the specific lists your check flagged - never pay third-party 'delisting services', which is a known scam pattern.
What blocklists can and cannot tell you
A listing on a major list (Spamhaus, Barracuda) has real operational impact and deserves immediate attention. A listing on a small, rarely-used list may mean nothing at all for your deliverability - which is why a good checker reports each list separately and marks unreachable zones as inconclusive instead of folding them into 'clean'.
Treat blocklists as one signal among several: a clean result does not certify an IP, and a minor listing does not condemn one. The aggregate picture - which lists, what codes, how stable over time - is what actually informs the decision.
The takeaway
Check your sending IPs before there is a problem, read a listing as a symptom rather than a verdict, and fix the cause before asking for removal. The DNSBL system is blunt, but it moves fast for operators who understand it.
Your public IP address and network location, detected automatically.
Loads automatically when you open NetChecks — no input needed. Use the Refresh button to re-check after switching networks or reconnecting your VPN.
Your browser
All-in-One Scan
Runs every relevant check against one IP or hostname in a single pass: DNS, whois, ping, traceroute, a well-known-ports scan (1-1024), HTTP headers and the SSL certificate.
Enter a domain or IP address and run it to check DNS, whois, ping, traceroute, common ports, HTTP headers, and the SSL certificate all at once.
Most checks run in parallel - typically finishes in about 30 seconds, longer if the target is slow or unreachable.
The port scan step only runs once the consent checkbox above is checked - every other check runs regardless.
Ping
Send ICMP echo requests to a host to check reachability and latency.
Enter a hostname or IP address and press Ping to send ICMP echo requests and measure round-trip latency.
Learn more about Ping
What it is
Ping sends ICMP Echo Request packets to a host and measures how long it takes for ICMP Echo Reply packets to come back. It is the most basic network connectivity test there is: it answers exactly one question, "is this machine reachable, and how quickly?" The ICMP protocol (RFC 792) was designed back in 1981 specifically to carry control and diagnostic messages over IP networks, outside of any application traffic - Ping is its best-known and most universally available implementation, present on virtually every operating system and network device since their earliest versions.
How it works
Every ICMP packet carries a TTL (Time To Live) field decremented by one at each router it crosses; if it hits zero before reaching the target, the packet is dropped and an error is sent back to the sender. The round-trip time (RTT) measured in milliseconds reflects the cumulative network latency over the entire round trip, not just the last leg near the target - a point that is often misunderstood, since slow ping results can have their root cause anywhere along the path, not necessarily near the server being tested. A ping typically sends several packets in a row rather than just one, which lets you tell a one-off latency spike apart from a recurring problem and calculate a packet loss rate over the sample.
Reading the results
A stable, low RTT - a few milliseconds on a local network, 10 to 50 ms for a destination within the same country, and noticeably more for an intercontinental link - indicates a healthy connection. Even a small amount of packet loss (above 1-2%) is particularly damaging for latency-sensitive uses like VoIP or interactive remote sessions, where every dropped packet shows up as a glitch or audible cutout. Highly variable latency from one packet to the next (jitter) is often more of a problem for these same use cases than latency that is high but perfectly stable. "Request timed out" means no reply arrived within the allotted time - the host could genuinely be down, a firewall could be silently blocking ICMP, or a route could be broken somewhere along the path; "Destination unreachable" is different and more informative: an intermediate router explicitly sent back a message saying it could not forward the packet, which helps narrow down where the problem actually sits.
Common mistakes
The most common misreading is concluding a host is "down" the moment a ping fails, when in fact a great many servers and devices - especially behind a properly hardened firewall, or hosted with major cloud providers - deliberately block inbound ICMP as a matter of policy while being fully operational and reachable on their actual services (HTTP, a database, and so on). A missing ping reply is therefore only meaningful evidence of downtime when combined with other signals, such as the application itself also failing to respond. Conversely, a successful ping is no guarantee whatsoever that the application service hosted on that machine is working correctly - these are two entirely independent layers of the network stack.
When to use it
The first thing to check before escalating a ticket: does the machine respond at all, before digging any further? Confirming connectivity after a firewall rule or routing table change, to make sure the change did not break access. Establishing a baseline latency measurement before a VoIP rollout or a carrier link failover, so there is an objective point of comparison if call quality complaints come in later. A lightweight, low-overhead periodic health check for an MSP monitoring several client sites in parallel, always as a complement to - never a replacement for - deeper application-level monitoring.
Traceroute
Trace the network path (hop by hop) to a destination host.
Enter a hostname or IP address and run it to see every network hop between this server and the destination, with latency per hop.
DNS Lookup (Nslookup)
Query DNS records: A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, SRV, CAA.
Enter a domain, choose a record type (A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, SRV, or CAA), then look it up.
Whois
Look up registration information for a domain or IP address.
Enter a domain or IP address to look up its registration details — registrar, owner organization, and important dates.
Blacklist Check
Check whether an IP address or domain is listed on public spam/abuse blocklists (DNSBL).
Enter an IPv4 address or domain and run it to check 7 public DNSBL/RBL blocklists at once - each shows as listed, not listed, or check failed.
TCP Port Scan
Check whether TCP ports are open on a host or IP: common ports, a custom list, or the full 1-65535 range.
Enter a host or IP, pick common ports, a custom list, or the full range, then scan to see which TCP ports respond.
A full range scan can take up to ~100 seconds. Large scans (more than 100 ports, including custom ranges/lists) are limited to 1 per minute per visitor.
Open ports (0)
HTTP Header Inspector
Fetch the HTTP response status and headers for a URL.
Enter a URL to fetch its HTTP response status code and every response header the server sends back.
SSL / TLS Certificate Checker
Inspect a host's TLS certificate: issuer, validity dates, and days remaining.
Enter a hostname to inspect its TLS certificate — issuer, validity dates, and days remaining before it expires.
Geo-IP Lookup
Look up the geographic location and network info for an IP address. Leave empty to look up your own public IP.
Enter any IP address, or leave it empty to look up your own, to see its approximate location and network/ISP info.
Computed entirely in your browser — no data sent to the server.
Enter an IP address and CIDR prefix (e.g. 192.168.1.0/24) to instantly compute the network range, broadcast address, and usable host count.
Speed Test
Basic download/upload throughput test against this server (accuracy depends on the server's own uplink).
Press Start to measure download and upload throughput against this server. Accuracy depends on this server's own connection.
Country Code Dictionary
ISO 3166-1 alpha-2 country codes — searched entirely in your browser.
Search or browse the list of ISO 3166-1 alpha-2 country codes, looked up entirely in your browser.
Country
ISO Code
Phone Dialing Code Dictionary
International calling codes by country — searched entirely in your browser.
Search or browse international calling codes by country, looked up entirely in your browser.
Country
Dial Code
World Clock
Pick a time zone to see the current time — drag the globe to spin it.
Pick a time zone from the list, or drag the globe, to see the current time there.
Your time
--:--:--
—
—
Selected time
--:--:--
—
—UTC±00:00
Difference vs. you—
—
Drag to rotate the globe.
French Mobile Network Status
Mobile antenna sites down or under maintenance in France, by operator (Orange, Free, SFR, Bouygues Telecom), from ARCEP's public data. Snapshot updated once a day by ARCEP - not a minute-by-minute feed.
Browse mobile antenna and fibre outage data by French operator — no input needed, updated automatically from ARCEP's public data.
Source: ARCEP, "Sites indisponibles" dataset, published under Licence Ouverte / Etalab 2.0 - commercial reuse explicitly allowed, unlike the IODA/CAIDA data this tab used before. The Normal/Watch/Alert badge is an in-house estimate (today's outage count vs. the median of prior days), not an official ARCEP classification. Source links below.
Most affected departments
Number of sites currently down or under maintenance, by department. Click an operator above to filter.
Fibre (FTTH) network quality by operator: reported-outage rate and connection-failure rate, from ARCEP's public data. Monthly indicators, 6-month rolling average - not a live feed like the mobile section.
Source: ARCEP, "Qualité des réseaux en fibre optique" dataset, published under Licence Ouverte / Etalab 2.0 - commercial reuse explicitly allowed. Source links below.
By operator (parent group)
Averages over the last 6 available months, per infrastructure-operator parent group.
NetChecks is provided for legitimate network diagnostics and educational purposes only, on systems, domains, and IP addresses that you own or are explicitly authorized to test.
Running port scans, DNS/whois lookups, traceroutes, or other checks against third-party systems without authorization may violate computer misuse laws in your jurisdiction (for example the Computer Fraud and Abuse Act in the US, the "Loi Godfrain" in France, or equivalent local legislation). You are solely responsible for ensuring you have the right to test any target you enter here.
This site and its results are provided "as is", without warranty of any kind. The operator of this site accepts no liability for any direct, indirect, or consequential damages, legal consequences, or misuse arising from the use of this site.
Requests are rate-limited to prevent abuse. The operator of this instance may optionally enable request-activity logging - if so, each tool request (your IP address, timestamp, the tool used, and the target/query entered) may be recorded in a database for security, abuse-prevention, and usage-analytics purposes; this is disabled by default. By using this site you agree to these terms; if you do not agree, do not use it.
Programmatic (API) use of this site is subject to these same terms, including the authorization requirement above.
Send feedback
Report an issue, leave a comment, or suggest a new feature.
This site uses ads and, if you accept, ad-partner cookies to help fund hosting. You can decline and keep using every tool ad-free.