Introduction

Shared hosting environments use a single IP address for multiple tenants' email sending. If one tenant sends spam, the shared IP can be blacklisted by Spamhaus and other DNSBL providers. This causes all email from that IP -- including legitimate emails from other tenants -- to be rejected by receiving mail servers, resulting in bounced emails and delivery failures.

Symptoms

  • Outgoing emails bounce with 550 Blocked by Spamhaus or IP blacklisted
  • Email headers show X-Spamhaus: listed in SBL/CSS
  • Multiple unrelated domains on the same hosting are experiencing email delivery issues
  • Spamhaus lookup shows the shared IP is listed
  • Error message: 554 5.7.1 Service unavailable; Client host [x.x.x.x] blocked using sbl.spamhaus.org

Common Causes

  • Another tenant on the shared hosting server is sending spam
  • Compromised website on the shared server being used as a spam relay
  • Shared IP has a history of abuse from previous tenants
  • Hosting provider not monitoring and responding to blacklist listings
  • No SPF, DKIM, or DMARC configured to identify legitimate senders

Step-by-Step Fix

  1. 1.Confirm the IP is blacklisted by Spamhaus: Check the listing status.
  2. 2.```bash
  3. 3.# Check Spamhaus listing
  4. 4.dig +short x.x.x.x.zen.spamhaus.org
  5. 5.# Non-empty response means listed (127.0.0.2 = SBL, 127.0.0.4 = XBL)
  6. 6.`
  7. 7.Check the listing reason on Spamhaus: Understand why the IP was listed.
  8. 8.```bash
  9. 9.# Visit https://check.spamhaus.org/ with the IP address
  10. 10.# Review the listing reason and date
  11. 11.`
  12. 12.Contact the hosting provider to request delisting: The IP owner must request removal.
  13. 13.`
  14. 14.# Open a support ticket with the hosting provider:
  15. 15.# - Provide the Spamhaus listing details
  16. 16.# - Request they investigate the source of spam on the shared IP
  17. 17.# - Ask them to submit a delisting request to Spamhaus
  18. 18.`
  19. 19.Configure SPF and DKIM to improve email reputation: Identify your domain's legitimate email.
  20. 20.```dns
  21. 21.# SPF record
  22. 22.example.com. IN TXT "v=spf1 include:_spf.hosting-provider.com ~all"

# DKIM: configure through cPanel > Email Deliverability # Generate DKIM key and publish the DNS record ```

  1. 1.Consider using a dedicated IP or third-party email service: Avoid shared IP reputation issues.
  2. 2.`
  3. 3.# Options:
  4. 4.# - Request a dedicated IP from the hosting provider
  5. 5.# - Use SendGrid, Mailgun, or Amazon SES for transactional email
  6. 6.# - Configure SMTP relay through a reputable email service
  7. 7.`

Prevention

  • Monitor shared IP reputation regularly using mxtoolbox.com or similar tools
  • Configure SPF, DKIM, and DMARC for all domains on the hosting account
  • Use a dedicated IP address for email if sending volume justifies the cost
  • Monitor email bounce rates and investigate spikes immediately
  • Report spam activity from other tenants to the hosting provider promptly
  • Use third-party email delivery services for critical transactional emails