senderscope

Guides · 8 min read · updated Nov 16, 2026

How to Check if an Email Address Is Valid Without Sending

Sending to dead addresses hurts your sender reputation, and a fake address at sign-up pollutes your data. Here's exactly how email validation works, step by step, and what each result means.

Valid isn't the same as deliverable

An address can be valid (correctly formatted, on a real domain) and still undeliverable (the mailbox was deleted). Checking properly means going through four layers, from cheapest to most informative.

1. Syntax

The address must have one @, a local part and a domain with a dot, without spaces or illegal characters. Most typos (jane@acme,com, jane@@acme.com) fail here. Also catch the common domain misspellings: gmial.com, hotmial.com, outlok.com, yaho.com.

2. Domain exists

Look up the domain in DNS. No A or MX record, no mail. A domain registered last week deserves extra caution if the email claims to be from an established company.

3. MX records

MX records name the servers that receive mail for the domain. They also reveal the provider:

MX record containsProvider
google.com / googlemail.comGoogle Workspace
outlook.com / protection.outlook.comMicrosoft 365
pphosted.com, mimecast.comSecurity gateway in front of the real provider
zoho.comZoho Mail

On macOS or Linux, run dig MX acme.com +short; on Windows, nslookup -type=mx acme.com.

4. SMTP mailbox check

The decisive step. A verifier connects to the MX server and begins an SMTP conversation: HELO, MAIL FROM, RCPT TO:<jane@acme.com>. The server answers 250 (accepted) or 550 (no such user), and the verifier disconnects with QUIT before sending any message. The recipient never sees anything.

Doing this yourself from a home connection rarely works: residential IP ranges are blocked on port 25 and servers distrust unknown senders. Verification services run dedicated, well-reputed infrastructure, which is why they return clearer answers.

The tricky results

  • Catch-all: the server accepts every address at the domain, including made-up ones. Verifiers detect it by testing a random address. A catch-all result means 'can't confirm', not 'invalid'.
  • Greylisting and timeouts: some servers temporarily refuse unknown senders. A good verifier retries; otherwise you'll see 'unknown'.
  • Disposable addresses: Mailinator-style inboxes are valid and deliverable, but nobody reads them for long. Block them at sign-up.
  • Role accounts: info@ and sales@ are valid, but they reach a team, not the person you think.

What to do with each verdict

VerdictCold outreachSign-up formVendor email
DeliverableSendAcceptProceed, still check the domain
Catch-allSend in small batchesAccept, confirm by emailCheck the domain carefully
RiskyHoldAccept with confirmationVerify by phone
UndeliverableRemoveReject, ask to retypeTreat as suspicious
DisposableRemoveRejectTreat as suspicious

Check one now

Paste any address into the email verifier. It runs the full chain (syntax, DNS, MX, SMTP, catch-all and disposable detection) and adds the SPF and DMARC status of the domain. Ten checks a month are free; lists go through the bulk tool.

Keep your lists clean

Re-verify lists older than three months before a campaign; roughly 2% of business addresses go stale every month as people change jobs. Keep hard bounces under 2% of sends, and remove any address that hard-bounces once.