Black Friday: 20% off every credit pack with code BF2026, through Cyber Monday, November 30. See pricing

An invalid email address is one that can't receive mail: it's malformed, or its domain or mailbox doesn't exist. Invalid email addresses get onto every list sooner or later, and each one you send to will normally come back as a hard bounce.
By the end of this guide you'll have found the invalid addresses on your list, fixed or removed them, and set things up so fewer new ones get in. You need your list as a CSV or Excel file and an email verifier. A free CampaignKit account gives you 200 validations, no credit card required.
An invalid email address is an address that mail can't be delivered to. Either it isn't written as an email address at all, or it looks right but nothing on the other end receives it. In both cases, sending to it normally produces a hard bounce.
Here are a few invalid email address examples:
| Example | What's wrong | Kind |
|---|---|---|
name@@example.com |
Two @ signs | Malformed |
jane doe@example.com |
Contains a space | Malformed |
name@gmial.com |
A typo of a well-known provider | Looks fine, wrong domain |
sales@no-such-company.invalid |
The domain doesn't exist | Looks fine, nothing receives it |
former.employee@example.com |
The mailbox was deleted | Looks fine, nothing receives it |
"Invalid" is not the same as "risky". A disposable address or a role address like info@ can receive mail; whether you want it on your list is a separate decision, covered in step 2.
When a tool or an email platform says an email address is invalid, it means one of two things.

The address breaks the rules for how an email address is written: a missing @, two @ signs, spaces, or a domain without an ending. An invalid email address format is the easiest kind to catch, because you can see it without contacting anyone. The rules themselves are in our guide to valid email address format.
The address is written correctly, but the domain doesn't exist, or the domain exists and the mailbox doesn't. This is the more common kind on a real list, and the one you can't spot by eye: former.employee@example.com looks exactly like a working address.
If a sign-up form rejects your own address, the form's check can be stricter than the actual rules, for example about plus signs or newer domain endings. The valid email address format guide shows what a correct address may contain, so you can tell whether the problem is your address or the form.
Most invalid addresses arrive in one of these ways:
gmial.com, or misses a letter in their name. The address is wrong from day one.Old and bought lists can also contain spam traps, addresses that exist only to catch senders with poor list hygiene.
Every invalid address you send to will normally come back as a hard bounce. Mailbox providers notice when a sender keeps mailing addresses that don't exist, and that can weigh on your sender reputation. A weaker reputation can mean more of your mail goes to spam or gets blocked, including mail to your valid subscribers.
To read more about how bounces affect your reputation, what counts as a high bounce rate and what Google expects from bulk senders, see our guide to email bounce rates. For what the bounce message itself means, such as a 550 for an unknown recipient, see SMTP bounce codes and how to respond.
There are two places to build your invalid email address list from.
Your email platform keeps a list of addresses that already bounced. In SendGrid, for example, the invalid emails page lets you pick a date range, download the list by choosing Download CSV under the gear icon, and select entries to remove (Twilio docs, checked November 2026). Other platforms have a similar bounce or suppression list.
This only finds addresses you've already sent to and that already bounced. It can't tell you about the rest of the list.
To find invalid addresses before they bounce, run the list through an email verifier.
The bulk email verifier page covers file formats, size limits and how to lay out your file.
Every address gets a score from 0 to 10. These reference points are the ones you'll see most often:
| Score | What it means |
|---|---|
| 0 | The email will bounce. |
| 2 | The email can be used, but it looks risky, for example a temporary (disposable) address. |
| 6 | The mail server didn't let us verify the mailbox (verifyRejected), so its existence is unconfirmed. |
| 9 | The address passed, but its domain is catch-all, so this mailbox can't be confirmed individually. |
| 10 | The address passed all checks, and the server will accept email for it. |
When an address doesn't get a clean pass, the result code tells you why. Here's what to do with each one:
| Result code | What it means | What to do |
|---|---|---|
syntax |
The address isn't correctly formatted. | Invalid: remove, unless the contact can give you the correct address. |
domain |
The domain doesn't exist or has no MX record. | Invalid: remove. |
mailbox |
The mail server reported the recipient as unknown. | Invalid: remove. |
didYouMean |
The address failed, and the result suggests a correction. | Fix it (step 3), then re-verify. |
disposable |
The address belongs to a temporary email service. | Risky: usually remove. |
role |
A role-based address such as sales@ or info@. |
Decide: keep it if a role inbox is a fair contact for what you send. |
catchAll |
The domain accepts mail for any address, so this mailbox can't be verified on its own. | Deliverable but unconfirmed: keep in a separate segment. |
verifyRejected |
The recipient's mail server didn't let us verify the mailbox. | Unconfirmed: keep in a separate segment, or leave it out of large sends. |
Treat three groups differently. Score 0 with syntax, domain or mailbox is invalid, so it goes. disposable and role are risky, so you decide. catchAll and verifyRejected are unverifiable: they may well be fine, but no check can prove it. For more on that last group, see what catch-all emails are and whether to send to them.
Some invalid addresses belong to real people who mistyped them. Those are worth saving.
didYouMean suggestion as a lead, not an answer. If name@gmial.com comes back with a suggested name@gmail.com, confirm with the contact before you change it, where you can.Don't repair addresses by guessing. Changing jane.doe@ to janedoe@ because it "looks more likely" can send your mail to a stranger.
Once you know which addresses are invalid, take them out of your sending list. To delete invalid email addresses with CampaignKit's results:
Whether you delete invalid addresses or suppress them is your policy choice. Deleting keeps the list small. Suppressing keeps a record, so the same address can't be re-imported from an old spreadsheet and mailed again. Either way, stop sending to them.
There are platform-specific walkthroughs for cleaning a Mailchimp list and cleaning a Klaviyo list, and the general guide on how to clean your email list.
Download your results soon after the job finishes: bulk validation jobs are deleted 30 days after they're created.
Cleaning a list once doesn't keep it clean. New invalid addresses come in through the same doors as before, so close them:
Re-verify a sample of the cleaned list, or the whole list if it's small. You should see no score-0 rows. If a few appear, those addresses went dead between the two runs or came in through a separate import; remove them as well.
Then watch the hard-bounce rate on your next send. It should drop compared with sends before the cleanup. It won't necessarily reach zero, because catch-all and unverifiable addresses can still bounce, and any address can stop working after you checked it.
A valid-looking address scored 6. The result code is verifyRejected: the recipient's mail server didn't let us verify the mailbox. The address may be fine. It just can't be proven, so keep it in a separate segment rather than deleting it.
A catch-all address passed but still bounced. A catch-all domain accepts mail for any address, so the individual mailbox can't be confirmed. A score of 9 means "deliverable, not confirmed", not a delivery guarantee. Watch the bounce rate of that segment.
An address verified last quarter bounced today. Addresses go dead over time. Re-verify before big sends, and pair verification with a sunset policy for contacts who stopped engaging.
The job's results are gone. Bulk validation jobs are deleted 30 days after they're created. Re-run the list if you need fresh results, and download the CSV promptly next time.
It means mail can't be delivered to that address. Either it isn't a correctly written email address, or its domain or mailbox doesn't exist.
Not quite. An invalid address is the cause; a hard bounce is what happens when you send to it. Bounces can also have other causes, such as a full inbox or a block against the sender, where the address itself may be fine.
A malformed address can't, though the person may give you a corrected one. A deleted mailbox or a dead domain could in theory be set up again, but treat it as gone, and only re-add it if the contact gives it to you again and it passes verification.
Verify the list, download the results without the undeliverable addresses, and import that cleaned file back into your email platform. Or import the undeliverable addresses as a suppression list, so they aren't mailed again.
Start with a spot-check: paste a few addresses into the free email verifier. Then verify your list with 200 free validations, no credit card required. After that, pricing is pay-as-you-go, and credits never expire. For a quick overview of the process, see email list cleaning.
Start with 200 free validations. Upgrade only when you're ready.
No credit card required • Cancel anytime