Run an IP blacklist check for a mail server
An IP blacklist check investigates whether named mail lists currently list a sending address. Use the public outbound mail-server IP identified in a delivery notice or by your mail administrator. Your browser’s public address may be unrelated.
Read more
Two sources are queried: SpamCop SCBL and Passive Spam Block List (PSBL). Other recipient policies and commercial lists remain outside coverage. The result never claims that every mail filter has been checked.
Paste one public IPv4 address and select Check two mail lists. Email addresses, domains, URLs and port suffixes are rejected. Example fills an address without submitting it.
IPv6 input is accepted only to show the unsupported coverage explicitly. Neither source is queried for IPv6 here. Mapped IPv4 is normalized; private and special-use addresses are rejected.
Our server uses Google Public DNS. Query names encode the entered IPv4 address, so the resolver and potentially list operators receive target-related DNS questions. This is not a test of your configured DNS resolver.
Read each source independently
A Listed by this source result means the mail-list check received a recognized positive answer for that address, after source controls passed. It does not identify a person or establish why an individual message was sent. Read the operator’s criteria and compare the result with actual mail logs before changing service configuration or making an accusation.
Read more
A Not listed in this response result means the mail-list check received an expected negative DNS response with the required evidence for that source. The wording is deliberately limited to the response received. It does not mean that every receiver will accept your mail, that the address was never listed, or that other reputation systems have no information about it.
A Listing status not established result means the mail-list check could not safely interpret that source. Causes include unsuccessful controls, resolver errors, rate limits, unexpected return codes, malformed answers, or timeouts. Retrying later may help, but repeatedly submitting requests immediately can worsen a rate limit. An unavailable source never adds a positive or negative verdict to the report.
Each source keeps its observation time. DNS caches can return previously obtained records, so different resolvers may temporarily disagree. Time identifies this service’s observation, not a spam report’s original event.
Expand evidence to see query name, response code, returned codes, controls and TTL. Zero TTL is valid. Cache lifetime is neither listing age nor a guaranteed removal countdown.
Copy exports JSON with the address, source links, controls, timestamps and evidence. Review operational details before sharing. There is no aggregate safety score.
Why an IP blacklist check needs controls
Each source first receives known-positive and known-negative control questions. Both must pass before the target is queried, helping identify a broken or misleading query path.
Control inputs are 127.0.0.2 and 127.0.0.1; these are DNS questions, not socket connections to loopback. RFC 5782 describes DNSBL conventions. Passing controls does not certify the complete dataset.
A failed control stops that source’s target query in the mail-list check. The other source can still finish independently. This means you might see one useful result and one unavailable result. Keep the distinction instead of collapsing the entire response into “clean,” and record which list was actually checked if you share the outcome with a mail administrator.
What this IP blacklist check cannot establish
Only expected listing codes are recognized. Access-restriction codes, unexpected owners, aliases and malformed responses remain unavailable. Another source can finish independently when one fails.
Read more
For a listing, read the operator’s linked guidance, investigate the mail service you administer and follow the appropriate review process. Only the operator controls its policy; this site neither removes entries nor charges for removal.
An IP blacklist check investigation workflow
Use the mail-list check alongside the delivery notice, rather than as a replacement for it. First identify the outbound address and the recipient’s stated rejection reason. Then compare the named list with the sources available here. If the notice cites a different source, a negative result on these two lists does not contradict the notice.
For DNS configuration questions beyond a mail-list check, use DNS lookup to inspect published records and reverse DNS lookup for PTR information. Merely finding a TXT record is not a full SPF, DKIM, or DMARC validation. Likewise, a PTR record is not evidence that a sender is authorized to use a particular domain.