All posts

What Happens If You Email an Address That Doesn't Exist?

··3 min read

If you email an address that does not exist, the receiving mail server normally refuses the message and your sending tool records a hard bounce. The person you meant to reach never sees it, and the bounce counts against your sender reputation. One stray address does little harm; a list full of them is how senders get paused.

This post walks through what happens, why a few bad addresses slip through without any bounce, and what to do before you press send.

What happens, step by step

  1. Your tool hands the message to the receiving server. It opens a connection to the mail server for the domain after the @ sign and names the recipient.
  2. The server checks the mailbox. If the user does not exist, many servers answer straight away with a permanent error, commonly a 550 code with text like "user unknown" or "recipient address rejected". Our page on 550 5.1.1 user unknown shows the common wordings.
  3. Your tool records a hard bounce. Most tools stop emailing that address after the first hard bounce and add it to a suppression list. Some, however, let you keep sending if you import the address again.
  4. The bounce rate for the send goes up. That rate is what your tool, your ESP and the mailbox providers look at. Bounce rate thresholds by platform explains what each one flags.

Some servers accept the message first and send a bounce notice later. That is why a bounce can arrive minutes after the send, not only during it.

When there is no bounce at all

Not every bad address announces itself:

  • Catch-all domains accept mail for any name, so a made-up address appears to work. The message may land in a shared inbox or be dropped. See what a catch-all domain is.
  • Silent drops. A few servers accept and discard mail for unknown users to avoid revealing which addresses exist.
  • Typos on real domains. A person typing "gmial.com" may reach a domain someone else registered. Use the email typo corrector to catch common cases.
  • Soft failures. A full mailbox or a temporary block returns a soft bounce, which looks different from a missing address. Read hard bounce vs soft bounce to tell them apart.

So "no bounce" is not the same as "delivered and read". It only means nobody told you it failed.

Why this matters more than it looks

A bounce is a free signal for the mailbox provider: you sent to an address that was never valid. Repeating it suggests the list was bought, scraped or never cleaned. Older lists collect more of them. Addresses typed in by hand on a form collect typos. Contacts who changed jobs leave closed mailboxes behind.

None of that shows up in your sending tool until the send is already out. By then the bounces are counted.

How to find these addresses before sending

  1. Remove duplicates with remove duplicate emails so you do not count one bad address twice.
  2. Fix obvious typos such as gmial.com and hotnail.com.
  3. Run a verifier. It asks the receiving server whether the mailbox exists without sending a message. Addresses marked invalid are the ones that would have bounced.
  4. Decide what to do with the middle results. Catch-all and unknown addresses cannot be confirmed either way. Our guide to accept-all vs unknown results covers how to treat them.
  5. Send a small batch first, then the rest if the bounce rate is clean.

For a full routine, follow the clean list before campaign checklist.

Already sent and seeing bounces?

Stop and look at which addresses bounced and why before the next send. What to do after a high bounce rate gives the steps, and the bounce message analyzer groups raw bounce messages by cause.

Check the list before you send

Run your first 100 addresses free on the verify page: sign in with Google, no card. If the sample shows invalid addresses, the rest of the list has them too. Pro is $39 a month with unlimited email verification*, so you can clean the whole file and re-check it before every send. See pricing.

*Fair use: the first 100,000 checks a month run at full speed, then slower, never cut off.

Common questions

Will the sender always get a bounce message back?

Usually, yes. The receiving server rejects the message during delivery or accepts it and sends a non-delivery report afterwards. Your sending tool turns that into a bounce event. A few setups drop mail without telling anyone, and catch-all domains accept the message and then it goes nowhere useful, so no bounce is not proof that someone read it.

Does one bounce hurt my sender reputation?

One bounce on its own is not a crisis. Providers and sending tools look at the rate across a send and the trend over days. Even so, repeatedly mailing addresses that do not exist is one of the clearest signs of a list nobody checked.

Can someone else receive the email if the address does not exist?

Normally no, because the server refuses it. The exception is a typo that lands on a real mailbox, such as a misspelled domain that someone else owns, which is why typo fixing matters before a send.

How many bad addresses can I send to before something happens?

There is no safe published number that applies everywhere. Sending tools and mailbox providers each set their own limits and change them. Aim for as close to zero hard bounces as you can get, and see our guide to bounce thresholds for the figures each platform shows.

Check your list before you send

Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.