Email Verification: How to Check if Email ID Valid or Not

Check the format, the MX records, then whether the mailbox accepts mail. A missing website does not make the address unusable.

Written by

Rajnish

Published on

6 min

To check if an email ID is valid, confirm three things in order: the address is shaped like an email, the domain has a way to receive mail, and the mailbox appears to accept it. An email ID here means the address, name@domain, not a phone number or a customer number.

A format check does not prove anyone can receive mail, and it does not require a dot in every technically valid address. The six methods below go from that look to a bulk verifier. A dead address bounces, and repeated bounces are a bad sign to the providers that decide where later mail lands. Verification drops those addresses before you send. It does not guarantee a reply.

How to Check if an Email Address Is Valid

Use the light methods for one address. Use a verification tool when you have a list.

Method 1: Use an email verification tool

This method is for a list. For one address, or a few, skip to method 2.

Upload the list, usually as a CSV, to a verification tool such as ZeroBounce, NeverBounce, Hunter, or EmailListVerify. The tool returns a label for each row. Labels differ by product. Read them with the MX and SMTP rules below before you delete a row or send to it.

A risky result is not a yes. On a catch-all domain the server accepts almost any name, so the check cannot prove that exact mailbox exists. Unknown means the check did not finish. Treat both as unconfirmed.

Manyreach sells email validation as a $24 a month add-on. It is not included in the sending plans.

Email verification results marking addresses valid, invalid, or risky

Method 2: Check the format (syntax)

A format check only looks at the shape. A normal public address looks like this:

username@domain.com

The local part is the name before @. The domain is the part after @. A normal check looks for one @ and no spaces. A typical public domain also has a dot, as in .com. A missing dot does not, by itself, make every address invalid. A name such as user@localhost can be technically valid and still have no dot. For mail you send on the public internet, you still want a domain that resolves. Failing a "must contain a dot" rule is not the same thing as "this address cannot exist."

Common syntax errors:

  • Missing the @ symbol, or typing two of them
  • Extra spaces or commas
  • Characters that usually do not belong in a business address, such as & or %
  • Domains like @gmaill.com or @outlook that look right but are wrong

An email format checker, online or in a spreadsheet, only tests this shape. Scan a column in Google Sheets or Excel for a missing @, a space, or a domain that is not one you can send to. A missing dot is a reason to look closer, not an automatic fail. Addresses that end in gmail.com can still be wrong before the @. A passed check means "this could be an email," not that the inbox exists.

Method 3: Look up the domain's mail servers (MX)

If the domain name does not exist, the email cannot be valid. A missing website does not tell you that. Plenty of domains receive mail and publish no site. A live site does not mean the domain accepts mail. No public page for the address is a separate question, covered in method 5.

How to read an MX lookup:

  • Take the domain, the part after @. For alex@acme.com, that is acme.com.
  • Look up its MX records. MX records name the servers that accept mail for that domain. A DNS lookup will show them, and so will a verifier. Setting MX on a domain you own is covered in how to set up MX records.
  • If MX records exist and name mail servers, the domain is set up to receive mail. That still does not prove this mailbox exists.
  • If DNS returns no MX records, SMTP can still deliver to the domain's own address record. No MX is not the same as no mail.
  • If the domain name does not resolve at all, the address is not usable right now.
  • Ignore whether a website loads. Use the MX result.

The next question is whether that exact recipient is accepted. That is an SMTP check, not a browser check.

Method 4: Send a test email

Sending a message is the direct test. Write a short note and send it. Read the bounce the way you would read an SMTP result. If it bounces because the user is unknown, the address is bad. A full mailbox or a temporary server problem means "not now," not "fake." No bounce is not a yes when the domain is catch-all.

This will not catch every problem. A catch-all domain accepts any name, so silence still does not prove the person exists. A server can also fail for a few hours and then accept mail. Bounces hurt the domain you send from, so test a few important addresses, not a whole list. For a list, use method 1.

Method 5: Search Google or LinkedIn

Paste the email into Google or LinkedIn. If the person publishes it on a company page, a speaker bio, or a profile, you have a public trace that they use this address.

A public match is a useful check. A missing match means "unknown," not "invalid." No site and no public record can still sit on a real mailbox. Plenty of real inboxes are never posted.

Method 6: Look for a profile photo or a contact card

In Gmail, and in some CRMs, hover an address. A photo, a name, or a company means some product has seen that address attached to a person.

It is a hint, not a proof. The photo can be old, and the mailbox can be closed. Use format, an MX lookup, and a verifier or one careful test send to see whether mail will land.

Contact card shown when hovering an email address

How to Read MX, SMTP, Catch-All, and Unknown

Each check answers a smaller question than "is this a real person?" Read the result you actually got.

MX lookup

An MX lookup asks DNS which servers accept mail for the domain. It does not ask whether that local part is a real mailbox. A domain with no website can still publish MX records and receive mail. A domain with a website can still have nowhere for mail to go.

SMTP outcomes

An SMTP check talks to one of those mail servers and asks it to accept the recipient, without sending the full campaign. You will see one of three outcomes:

  • Accept. The server says yes. On a normal domain, that is as close as a tool gets to "this mailbox exists." On a catch-all domain, the same yes does not prove the name is real.
  • Reject. The server refuses the recipient with a permanent error, such as user unknown. Treat that address as invalid.
  • Temporary or blocked. A temporary error, a timeout, greylisting, or a server that refuses the probe. That is unknown. It is not a hard bounce. Try again later, or leave the row out of a large send until you know.

Mailbox providers often refuse these probes. If the SMTP conversation does not finish, the honest label is unknown, not valid.

Catch-all domains

A catch-all, also called accept-all, takes mail for every name at the domain. The MX check can pass. The SMTP check can accept. You still do not know whether that person has a mailbox. Keep the row unconfirmed. Do not count it as verified, and do not delete it as if it had bounced.

Unknown

Unknown means you did not get a yes or a no. Causes include a timeout, a temporary error, a server that hides mailbox status, and a catch-all that the tool will not call valid. Do not delete unknown rows as if they bounced, and do not load them into a big campaign as if they were confirmed. For one important address, a careful test send can settle a temporary failure. For a list, leave unknowns out until a later check.

  • Syntax proves the shape only. A missing dot is not automatic proof that the address is invalid.
  • A website proves nothing about mail.
  • MX records show where mail for the domain should go. If none are published, check the domain's address record before you call it dead. MX does not prove this mailbox exists.
  • An SMTP accept is meaningful on a normal domain and weak on a catch-all.
  • An SMTP reject for an unknown user is the result that means invalid.
  • A test send proves a hard bounce. It costs a send on your domain.
  • Google, LinkedIn, or a profile card shows that someone published the address. A missing match is unknown, not invalid.

Reject bad syntax and domain names that do not resolve. Then run a verifier on what is left, and do not treat catch-all or unknown rows as confirmed.

After You Verify: What to Do Next

A clean list is the input, not the campaign. After the invalid rows are gone, do this with the ones you kept.

1. Segment the list

Do not send the same message to everyone. Split the list by what you know:

  • Behavior, such as opened a past email or never replied
  • Stage, such as a cold first touch or someone who already answered
  • Who they are, such as role, company type, or country

Then write a different note for each group, instead of one email to every address you kept.

2. Write a specific email

Use what you know where a stranger will notice it:

  • The subject, for example a first name and the company, not a generic offer
  • The first lines, with the problem that fits their role
  • The send time, set for their timezone rather than yours

Manyreach sequences support merge fields and custom variables, so those blanks can be filled per recipient.

3. Follow up on a schedule

One email is easy to miss. A short sequence can:

  • Reach people who did not answer the first note
  • Send the next step after someone asks for it, such as an onboarding note
  • Share a relevant example after a call, rather than a new pitch to the whole list

Stop the sequence when the person replies.

4. Watch the numbers that move

After you send, look at:

  • Open rate
  • Click-through rate
  • Reply rate
  • Bounce rate
  • Spam complaints

Bounces and complaints mean the check was incomplete or the list went stale. Opens and replies describe the copy. Change the subject, the body, the ask, or the send time. Do not write again to the same bad rows.

5. Check the list again before the next big send

People change jobs, abandon inboxes, and switch providers. Run verification again before a large campaign. Cold lists go stale faster than a list of current customers.

6. Stay within GDPR and CAN-SPAM

A valid address is not permission to write. Verification removes dead rows. It does not create consent.

On every campaign:

  • Say who you are
  • Include a way to opt out that works
  • Do not buy a random list and assume a verifier makes it lawful

Look up the rules that cover your send. Teams usually start with GDPR in the European Union and CAN-SPAM in the United States, then confirm what those texts currently require. A mailbox check is not that confirmation.

Why Email Verification Comes First

Fewer bounces means more of the mail can be delivered, which is the only way a prospect can see it.

1. Cut bounces

High bounce rates go together with weaker delivery. Verification removes addresses that would bounce, before those bounces pile up.

2. Protect the domain you send from

Sending into spam traps and dead mailboxes damages the trust of the sending domain. A cleaner list is one part you can fix before the campaign starts.

3. Stop paying to write to nobody

Building a list and writing the sequence costs time. Sending that work to addresses that cannot receive it wastes the send. Drop those rows first.

4. Give the campaign a fair read

The people who remain can receive the message, so opens and replies describe the copy, not a pile of dead addresses. Checking is not a promise that revenue will rise by a set amount.

Final Thoughts

Checking an email ID means checking the format, the mail servers, and the mailbox, in that order. A format checker answers only the first. A verifier is how you read the other two across a list, including catch-all and unknown results.

  • Reject bad syntax and domain names that do not resolve before you pay to verify the rest
  • Follow up only with addresses that passed, and stop when someone replies
  • Keep the list segmented, and check it again before a large send
  • Treat permission and list quality as two separate problems
Clean email list ready to send after verification

FAQs

How do I check if an email ID is valid or not?

Check the shape (name@domain), then the domain's MX records, then whether the mailbox is accepted. Do the first two for a single address. Use a verifier for a list. A missing website, or a missing dot, does not settle it.

Can I manually verify an email address?

Yes, for a few addresses: syntax, an MX lookup, a search, and one test if it matters. A test send creates bounces on your domain. A list belongs in a verifier. Read accept, reject, and unknown before you trust the result.

How do I check whether an email address is genuine?

Genuine means a real person can receive mail there. Pair a public trace (their site or LinkedIn) with an MX lookup and an SMTP result that is not catch-all or unknown. A hover photo is only a hint.

How often should I verify my email list?

Before a large campaign, and again when people on the list may have changed jobs. Do not wait for a spike in bounces.

What should I do after I find out the email is valid?

Segment the rows you kept, write to one person, and follow up only until they reply. A valid address still needs a reason to write and a way to opt out.

Luka Pecavar

About the author

Rajnish

Share Article

The Only Truly ‘Unlimited’ Cold Emailing Platform

Manyreach lets you connect unlimited mailboxes to send cold emails to unlimited contacts & add unlimited team members under unlimited workspaces.

Start for free now