How to verify an email address How to verify an email address

What does verifying an email address actually check?

Verification answers three questions: is the address written correctly, can its domain receive email, and does this exact mailbox exist? The address itself and public DNS records answer the first two. Only the receiving mail server knows the third, and many won’t say.

How do you check if an email address is valid?

1. 1

   Check the syntax

   A valid address has one @, a name before it and a domain after it. Under RFC 5321, the part before the @ can be up to 64 characters. Look for spaces, two dots in a row and typos like gmial.com or .con.

2. 2

   Confirm the domain exists

   Look the domain up in DNS. If it doesn’t resolve, it’s misspelled, expired or never existed, and nothing can be delivered to it.

3. 3

   Look up the MX records

   MX records name the servers that accept mail for the domain. A domain with a “null MX” record, defined in RFC 7505, is declaring that it accepts no email at all.

4. 4

   Flag disposable addresses

   Temporary inbox services hand out addresses that expire after minutes or days. Compare the domain against a maintained list of disposable providers, and drop matches from sales lists.

5. 5

   Flag role addresses

   Names like info@, sales@ and support@ reach a shared inbox, not one person. RFC 2142 defines several of them, including postmaster@ and abuse@, which exist for operations and complaints.

6. 6

   Decide how to test the mailbox

   You can ask the mail server directly with an SMTP check, or send a real message and watch for a bounce. Both have limits, covered below.

How do you look up a domain’s MX records?

You don’t need a tool. On Windows, open a command prompt and run nslookup -type=mx example.com. On macOS or Linux, run dig example.com MX +short.

Each result is a mail server with a priority number, and senders try the lowest number first. The host names often show the provider. Servers ending in google.com mean Google Workspace, and mail.protection.outlook.com means Microsoft 365.

No MX records at all is a warning sign. RFC 5321 lets senders fall back to the domain’s own address, but a domain set up for email normally publishes MX records. The DataPit verifier marks these addresses risky.

What are disposable and role email addresses?

A disposable address comes from a service that creates temporary inboxes, often for a single sign-up. It may stop working within hours, and nobody is waiting to read your message. In a sales list, it usually marks a fake or throwaway entry.

A role address belongs to a function rather than a person: info@, sales@, support@, billing@. It can be a good place to ask a question. For one-to-one outreach it’s a weak target, because it lands in a shared queue.

Addresses at free providers such as Gmail or Outlook.com are real and can be perfectly valid. For B2B outreach, they tell you the address is personal rather than tied to a company.

Can you verify an email address without sending an email?

Partly. Beyond DNS, the only way to test a mailbox is to ask its mail server. An SMTP check connects to the domain’s MX server, starts a message to the address, then hangs up before sending anything.

If the server answers with a 250 code, it accepted the recipient. A 550 reply means the mailbox is unavailable. SMTP also has a VRFY command for this, but sites may disable it, and a disabled server must answer 252, which confirms nothing.

Why are SMTP mailbox checks unreliable?

• Catch-all servers. Some domains accept mail for any name, real or not. The server says yes to every address, so the check proves nothing.
• Greylisting. Some servers turn away unfamiliar senders with a temporary 4xx error and wait for them to retry, as RFC 6647 describes. A one-off check gets a refusal, not an answer.
• Late rejections. Some servers accept every recipient during the SMTP conversation and reject the message only after it arrives. A check that hangs up early never learns the result.
• Blocking. Mail servers notice connections that test many addresses and never send. They may slow down or block the checking server.
• A mailbox isn’t a person. An address can keep working long after its owner has left, and some forward to a shared inbox.

That’s why the DataPit email verifier doesn’t probe mail servers. It reports what DNS and its lists can establish, and it says plainly that it can’t confirm the mailbox.

What’s the difference between a hard bounce and a soft bounce?

A bounce is the receiving server’s refusal, sent back to you as a message. Its SMTP reply code tells you which kind it is. RFC 5321 treats 5xx codes as permanent failures and 4xx codes as temporary ones.

Mailbox providers watch how you handle bounces. Yahoo’s sender guidance tells senders to monitor hard and soft bounces and to remove invalid recipients promptly. It also asks senders to keep their spam rate below 0.3%.

How do you clean an email list before sending?

1. 1

   Remove duplicates and fix typos

   Merge duplicate contacts, trim stray spaces and fix obvious domain typos like gmial.com.

2. 2

   Run every address through a verifier

   Remove the invalid ones. They will bounce, and bounces cost you sender reputation.

3. 3

   Review the risky ones

   Drop disposable addresses. Swap role addresses for a named person where you can, and recheck domains that timed out.

4. 4

   Send a small first batch

   Watch the bounce rate before you send the rest, and pause if it climbs. A catch-all domain can pass every check and still bounce.

5. 5

   Suppress bounces and opt-outs for good

   Never re-add an address that hard-bounced or asked to stop. In the US, CAN-SPAM requires you to honor opt-out requests within 10 business days.

6. 6

   Re-check old lists

   People change jobs and domains lapse. Verify a list again before you reuse it after a long gap.

Still looking for the address in the first place? See how to find someone’s email address.

Last updated September 28, 2026