// how to fix
Your sending IP address is on a blacklist
A blacklist is a public list of IP addresses known for sending spam. Find out if the IP is yours, fix the cause, then ask for removal.
What it means
Every email is sent from a server with an IP address, a number like 203.0.113.10. Blacklists (also called blocklists or DNSBLs) are public lists of IP addresses that sent spam or behaved suspiciously. Many receiving servers check them before accepting an email.
Why it matters
It depends on the list. Delivmail sorts them by impact:
- High impact (for example Spamhaus, Barracuda, SpamCop): used by many providers. A listing can cause rejections or spam placement.
- Low impact: rarely used by major providers like Gmail or Outlook. Worth knowing, rarely urgent.
How to check
Send a test email from the home page: the report checks the IP that actually delivered your email and tells you whether it looks like your own server or a shared provider. You can also look up any IP address on the Blacklist lookup page at /blacklists.
First: is it your IP?
Shared IP (Google, Microsoft, a newsletter tool, your web host's mail server)
If you send through Gmail, Outlook or a big email service, the IP is shared with many other customers. A listing is usually caused by someone else, and the provider is responsible for it.
- Do not request removal yourself: you do not control this IP.
- Check that your own account is not hacked: unexpected sent emails, unknown logins, strange forwarding rules.
- If your recipients report problems, contact your provider's support with the Delivmail report.
- For large volumes, ask your provider about a dedicated IP address.
Your own server or a dedicated IP
Here the listing is about your own sending. You must find and fix the cause before asking for removal, or you will be listed again quickly.
How to fix it (own server)
- Find the cause. The most common ones:
- A hacked email account sending spam (change passwords, enable two-factor login).
- A hacked website or plugin sending email in the background.
- A contact form abused by bots (add a captcha).
- A bought or old contact list full of invalid or trap addresses.
- A badly configured server that relays mail for anyone ("open relay").
- Stop the problem. Clean the server, block the abused account or form, and check your outgoing queue is empty of spam.
- Read the listing reason. Each blacklist has a lookup page that explains why the IP is listed and how to request removal.
- Request removal on each list's website, starting with the high-impact ones. For Spamhaus, use check.spamhaus.org.
- Be patient. Some lists remove you within hours, others expire automatically after a few days without spam.
Prevent it from happening again
- Only send to people who asked for your emails, and remove addresses that bounce.
- Make unsubscribing easy.
- Set up SPF, DKIM, DMARC and reverse DNS correctly.
Need a hand? Blacklist removal help is available in the paid Delivmail dashboard.
Check that it is fixed
Check the IP again on the Blacklist lookup page, then send a new test email from the home page. The blacklist section should be clean.
Check that it is fixed
DNS changes can take from a few minutes to a few hours. Then send a new test email or scan your domain again.
Related guides
- Move DMARC from p=none to quarantine or reject safelyp=none only watches. To really stop fake emails using your domain, move step by step to quarantine and reject, without blocking your own emails.
- Your domain is on a blacklist (Spamhaus DBL, SURBL, URIBL)Domain blacklists list domain names seen in spam. They follow your domain wherever you send from. Find the cause, clean up, then request removal.
- Bounce "550 5.7.1": message rejected or blocked by policyA 5.7.1 bounce means the receiving server refused your email on purpose. Learn to read bounce messages, find the real reason and fix it.
- Protect your incoming mail with MTA-STS and TLS-RPTMTA-STS forces other servers to use encryption when they deliver email to your domain. TLS-RPT sends you reports when that fails. Both are optional but recommended.
- Emails sent without TLS encryption (STARTTLS)Your server delivered the email in clear text, without encryption. Gmail flags this with a red padlock and expects bulk senders to use TLS. Turn on STARTTLS.