550 JunkMail Rejected: RBL on rbl.websitewelcome.com (HostGator / EIG)

SMTP error code 550: causes, retry logic, and the sender-side fix. JunkMail Rejected: RBL on rbl.websitewelcome.com (HostGator / EIG).
SMTPedia editorial team
Email infrastructure & deliverability editor
3 min read Updated Aug 27, 2026 25 views
Code550
Bounce typeHard bounce
RetryableNo (until delisted)
Action neededContact HostGator support
Typical error message
550-JunkMail rejected - x.x.x.x is in an RBL on rbl.websitewelcome.com

What does 550 JunkMail rejected, RBL on rbl.websitewelcome.com mean?

rbl.websitewelcome.com is the internal real-time blocklist (RBL) operated by Endurance International Group (EIG), the parent company behind HostGator, Bluehost, A Small Orange, iPage, Site5, Constant Contact, and many other shared hosting brands. When an EIG-hosted mail server returns this rejection, your sending IP is on their internal RBL. The list is fed by spam complaints from EIG customers, public DNSBL inheritance, and internal abuse detection. The list is not publicly queryable in the standard way and there is no self-service delisting form: removal requires opening a support ticket with HostGator (or whichever EIG brand the recipient uses) and providing evidence of remediation.

Is this a soft or hard bounce?

⚠️
Hard bounce affecting all EIG-hosted recipients

EIG operates a large share of shared US hosting infrastructure. A rbl.websitewelcome.com listing blocks delivery to HostGator, Bluehost, iPage, and related brands until removed.

Common causes

📣
Spam complaints from EIG customers

Marks-as-spam from HostGator/Bluehost/iPage mailbox users feed directly into the RBL.

Public DNSBL inheritance

EIG integrates Spamhaus, Barracuda, Abusix into its filtering. Public listings often propagate to the internal RBL.

🪹
Spam trap hits

EIG maintains spam trap addresses across its mailbox population. Hits result in immediate listing.

How to fix it

1
Verify public DNSBL status first

Look up your IP at Spamhaus, Barracuda, Abusix. Clearing public listings often resolves EIG automatically within 24 to 48 hours.

2
Open a support ticket with the relevant EIG brand

Submit through hostgator.com/contact or the equivalent for Bluehost / iPage. Provide your IP, sending domain, evidence of legitimate use, and remediation details.

3
Audit authentication

Confirm SPF, DKIM, DMARC all pass with strict alignment.

4
Clean list before retrying

Use email verification to remove invalid addresses. High bounce rate to EIG mailboxes is the strongest trigger for the RBL.

Provider-specific notes

EIG brandNotes
HostGatorMost prominent EIG brand for mail filtering. Use HostGator contact for delisting regardless of which sub-brand the recipient uses.
BluehostSame EIG infrastructure. Same RBL, same removal process.
iPage, A Small Orange, Site5, othersSame shared EIG infrastructure. Listing affects all EIG-hosted recipients simultaneously.
Pre-bounce verification

Prevent the bounces that hurt your sender IP

EIG internal RBLs react fast to bounce-driven reputation decay. SMTPing catches invalid addresses before you send, keeping your IP off shared-hosting blocklists. 25 free checks daily, no card required.

Try SMTPing free →

About the Author

Alaa - SMTPedia author

Alaa · LinkedIn

Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.


About SMTPedia

SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.

We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.