What 550 5.1.1 Means
550 5.1.1 is the standard enhanced status code for 'bad destination mailbox address.' Per RFC 3463, the recipient address you specified doesn't correspond to an actual mailbox at the receiving domain. It's a clean, definitive hard bounce.
Every major receiver. Gmail, Outlook, Yahoo, Microsoft 365, and most enterprise gateways all return 550 5.1.1 when the local-part of the address doesn't match any mailbox.
The address was never valid (typo, scraped wrong); the address was valid but the user left the company and the mailbox was deleted; the address was a personal alias that's been disabled; or the address was a catch-all that's been turned off.
How to Fix 550 5.1.1
- 1
Mark the address invalid in your CRM
550 5.1.1 is unambiguous — the address doesn't exist. Mark the prospect invalid, exclude from future campaigns, and don't retry. Most sending platforms (Instantly, Smartlead) auto-suppress hard-bounced addresses.
- 2
Audit your list source
A single 550 5.1.1 is noise. A 5-10% rate across a campaign signals a bad data source. If you bought a list, the vendor's data is stale; if you scraped, your collection logic is producing invalid addresses. Identify and remediate the source.
- 3
Pre-verify addresses before next campaign
Run your list through a verification service (NeverBounce, ZeroBounce, Hunter, BriteVerify) before sending. Verification services typically catch 8-15% of addresses as invalid on a cold list. The cost (typically $0.005-$0.01 per address) is far cheaper than the deliverability damage from sending to many bad addresses.
- 4
Watch your overall bounce rate
Most receivers tolerate up to 2-5% hard bounces per campaign without reputation impact. Above that, your IP starts getting deprioritized. Verify before send and your bounce rate stays well below the threshold.
- 5
Consider finding the prospect's current address
If the address was valid in the past (employee left), the prospect themselves might still be reachable at their new role. LinkedIn-based prospecting tools can refresh stale contact data. For high-value prospects, this is worth the effort.
References
550 5.1.1 in the Cold Email Context
550 5.1.1 rate is the cleanest measure of cold email list quality. Anything above 5% across a campaign signals you need to verify your list before sending. Receivers track per-domain bounce rates closely — Gmail's spam-folder placement degrades sharply once your bounce rate exceeds 4%. ColdRelay's bounce classification automatically suppresses 550 5.1.1 addresses across all your future campaigns at the infrastructure layer, so once an address bounces hard from one mailbox, no other mailbox in your account will send to it. This protects your sender reputation even when your sending platform's local suppression list is out of sync.
Frequently Asked Questions
Is 550 5.1.1 the same as a hard bounce?
Yes. It's the canonical hard-bounce code. The address doesn't exist and never will (at least not as the same mailbox). Sending platforms treat 550 5.1.1 as the cleanest signal to remove an address from active rotation.
Does 550 5.1.1 always mean the address never existed?
No. It means the address doesn't exist NOW. An employee may have left, an alias may have been disabled, or a catch-all may have been turned off. The address was potentially valid in the past.
How much does a high 550 5.1.1 rate hurt my reputation?
Significantly. Receivers track bounce rates as a primary reputation signal. Anything above 5% across a sustained send schedule moves you from 'good' to 'monitored' to 'throttled' on most major receivers. Keep bounces under 2% by pre-verifying.
Should I retry 550 5.1.1 after a few weeks?
No. The address won't reappear. If the recipient is genuinely important, find their new address — don't keep retrying the old one. Repeated sends to a hard-bounced address accelerate reputation damage.
Why do some receivers return 550 5.1.1 only for some addresses?
Receivers differ in whether they validate addresses at RCPT TO (immediate bounce) or after DATA (delayed bounce). Some use both — a syntactically-valid address goes through, but a non-existent one returns 550 5.1.1 at RCPT TO. The cause is the same; the timing differs.