Guides BLACKLIST

What is a blacklist (DNSBL)?

Is your mail being rejected? Learn how to check the sending IP and named blocklist, understand its reason and choose the right next step.

Mail from example.com is rejected and the rejection names a blocklist. Start with the sending server's IP and the reason given by that list. A list that returns this information through DNS is called a DNSBL. The receiver decides how to use its result.

Check the sending IPs from an email

First understand one rejection

Suppose you send mail for example.com from 192.0.2.44. The receiver rejects a message and names that IP and a blocklist. This is a fictional example.

The receiver has looked up the connecting IP on that list. In this example, the list says unwanted mail has been seen from that address. That gives the receiver a reason to refuse this connection.

Your administrator investigates what is sending from that IP and fixes the cause. They then follow the named list's official procedure to have the entry removed. This is called delisting. Check both the list and a new delivery attempt afterwards.

A result from a checker alone is not the same as this rejection. Receivers do not all use the same lists or respond in the same way. Start with the specific rejection you actually received.

Which IP should you investigate?

A message can pass through several servers. In an app → sending service → receiver chain, the final receiver usually sees the sending service's IP, not the app's. Start with the rejection or the Received line added by the trusted receiving mail server.

Fictional example: mx.receiver.example reports receiving the message from relay.sender.example at 192.0.2.44. An earlier Received line names the app at 198.51.100.23. For a block on the connection to this receiver, investigate 192.0.2.44. A listing of only the earlier app address does not by itself explain that block.

Earlier header lines can be untrustworthy. DNS Radar reads supplied headers but cannot prove who added them. If in doubt, ask the mail administrator to compare the actual receiving log or rejection. If a sending provider controls the IP, pass the details to that provider.

How to get off

  • Keep the actual rejection: which receiver, sending IP, list and reason does it name? A listing alone does not prove this receiver blocks because of it.
  • Check the reason on the list's official website. Determine whether it concerns abuse, an incorrect sending route or something else.
  • Fix that cause. For a shared IP or one managed by a service, involve the sending provider.
  • Follow the official removal procedure, also called delisting. Some lists remove entries automatically. Others require a request.
  • Check the list result again and ask the administrator to assess a new delivery attempt to the affected receiver.

A fee alone does not tell you whether you can ignore an actual block. Do not act on an unsolicited payment request. Use the official procedure and let the real rejection guide your response. Removal does not guarantee delivery or provide a lasting fix if the cause remains.

What the DNS Radar check does and does not tell you

The Mailheaders tool runs the blacklist check only when you choose it. The current public check uses selected public IPv4 addresses from the headers and a limited set of lists. It checks at most eight distinct eligible IPs and tells you if more were present. This check does not test IPv6 addresses.

Read the result for each IP and list:

  • Listed: the list returned a usable answer indicating a listing. Read the reason and the official list information.
  • Not listed: the check for this list completed without a listing. It says nothing about other lists or other traffic.
  • Unavailable: the list could not supply a usable answer for this check, for example because it rejects the DNS service used.
  • Check failed: an error leaves the result unknown. This is not a clean result.

Verify an important finding with the list itself too. A result applies to the addresses, lists and time tested.

Why you can end up on a list

Possible causes include:

  • An infected computer, compromised website or abused mail account sends unwanted mail.
  • You send to many invalid addresses, or recipients report your mail as spam.
  • Other users of the same sending IP cause trouble.
  • A misconfigured server lets others relay mail without permission: an open relay.
  • The address falls under a policy that does not allow direct delivery to final recipients.

The last case is the purpose of Spamhaus PBL, for example. Such an address is not necessarily involved in abuse. The intended route may be to submit mail to your provider with login credentials, letting its mail server deliver it onwards. Read the specific reason before assuming a compromise or requesting removal.

Domain lists such as Spamhaus DBL exist alongside IP lists. A domain listing and an IP listing are different results. Always check which target and list were examined.

Reputation is broader than blacklists

Receivers also consider their own reputation data, spam complaints, sending behavior and domain authentication. Keep SPF, DKIM and DMARC in order and send only to recipients who expect your messages.

These methods check specific domain identities and, for DMARC, their relationship to the visible sender domain. They do not prove that a person authorized the message or that its content is safe. Correctly authenticated mail can still be abusive and become listed.

Primary sources

Frequently asked questions

How do I know if I'm on a blacklist?

Use the optional blacklist check in the Mailheaders tool and read which IPs and lists were tested. Verify an important listing on the list's official website too. Compare it with the rejection you actually received.

I'm on one but I don't spam. How come?

A list may concern sending policy, you may share an IP with other users, or abuse may be happening without your knowledge. The list name and reason determine what to investigate. A listing alone does not prove a compromise.

Do SPF/DKIM/DMARC help against blacklisting?

They are part of good mail configuration, but do not remove an IP from a list or prove safe content or a trustworthy person. Fix the specific cause of the listing.

How long am I on a list?

It varies per list: some remove you automatically after a period without abuse, others require a manual delisting request. Always fix the cause first.

Check the sending IPs from an email →