IP blacklist check

Check a public IPv4 address against two named mail blocklists, with source health checks and clear limits.

Check the outbound mail server’s public IP. We send DNS queries through Google Public DNS to SpamCop and PSBL after you submit. This integration checks IPv4 only.

Only these two lists are checked. Not listed does not establish safety, mail delivery, or absence from other lists. IPv6 coverage is unavailable here.

Six lookups per minute per connection; shared service limits also apply. Up to six DNS queries per IPv4 lookup. Results remain in this tab unless you copy them.

No lookup has run.

Source results

SpamCop SCBL

Not checked yet

bl.spamcop.net

Source’s review or removal guidance

Passive Spam Block List

Not checked yet

psbl.surriel.com

Source’s review or removal guidance

Why mail-list checks include controls

  1. Identify the mail-server IP

    Use the address from the relevant delivery failure.

  2. Check source controls

    Require the known positive and negative DNS responses.

  3. Query named DNSBLs

    Ask SpamCop and PSBL through Google Public DNS.

  4. Read scoped outcomes

    Listed, not listed, unsupported and unavailable remain separate.

Each source is interpreted independently, after validating known positive and negative answers through the same resolver.
On this page

Learn more about IP blacklist check

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.

IP blacklist check questions

Does an IP blacklist check explain a website block?

A mail-list check here concerns two mail lists. A website can enforce its own policy for many unrelated reasons, including account state or traffic behavior. Compare the actual website error and contact its operator when appropriate. The mail-list response alone cannot explain a browser access decision, and changing networks does not correct every underlying account or service problem.

Which address belongs in an IP blacklist check?

Your browser and mail service can leave through different networks. A mail-list check should use the outbound address associated with the failed delivery, not assume that the browser’s current address is relevant. Webmail commonly delegates message delivery to provider infrastructure. A VPN used by your browser may have no effect on those servers’ outgoing connections.

Can an IP blacklist check guarantee delivery?

No. A mail-list check can describe only its named sources and current observations. It cannot guarantee a receiver’s future decisions or represent a source it did not query. Even the same recipient can handle two messages differently. Preserve the result’s scope when forwarding it to colleagues so that a narrow negative response does not become a broad promise.

Why does this IP blacklist check use two sources?

This mail-list check prioritizes explicit source coverage and interpretable responses. It currently includes SpamCop and PSBL, with controls on every IPv4 run. Additional providers can be added after their capabilities and usage conditions are reviewed. The count shown by this tool should always match implemented, named integrations rather than a marketing target.

What does stopping an IP blacklist check do?

Stopping the mail-list check stops waiting and invalidates the pending result in this tab. A request already received by the service or resolver may have begun processing; stop is not a promise to undo that work. Clear also resets the input and removes the displayed report. A late response cannot restore a report that you have cleared.

Where are the IP blacklist check sources documented?

The mail-list check implementation is documented on our methodology and data sources pages. Read SpamCop’s DNS query instructions, SpamCop’s list description, and PSBL’s usage documentation for the services’ own explanations. Source information was reviewed on September 28, 2026; policies and datasets can change after that review.

methodology

data sources

SpamCop’s DNS query instructions

SpamCop’s list description

PSBL’s usage documentation

Why does an IPv6 input not produce the usual list queries?

The integrations here do not provide IPv6 coverage. The page preserves that unsupported state rather than treating a query that was never made as unlisted. Ask the source about its supported address families before drawing a delivery conclusion.

Can this page remove a listed sending address?

No. It displays source-specific observations and does not control the source’s records. Investigate the reason and official process at the relevant list, while reviewing the sending service itself. A local retry does not submit a delisting request.