Free Email Validator: Check Any Email Address

What the checker looks at

An email address tells you very little on its own, but it is the first thing most sign-up forms collect. The checker above looks at the address and its domain, not at the person behind it. It is built on the same checks as the Email Validate API, so what you see here is what your onboarding flow can use automatically.

Paste an address, run the check, and read the result against the table below. Nothing about the check requires you to create an account.

What each result field means

The table describes the checks in plain terms. Exact field names and values in the live API response are set out in the product documentation, so treat this as a guide to interpretation, not a schema.

Validation is not verification

The two terms are often used interchangeably, but they describe different things.

• Validation inspects the address and its domain using format rules and DNS and provider data. No message is sent, the mailbox owner is never contacted, and the result comes back in the time it takes to make a request.
• Verification, in the sense of a confirmation email, sends a message with a link or code and waits for the user to act on it. That proves the user can access the inbox, which validation cannot.

The two work best together. Validation runs first, at the form field, so you do not send confirmation emails to addresses that cannot receive them or were never meant to. Confirmation then covers the cases validation cannot see.

How fraud and risk teams use it at sign-up

Email is cheap to create in bulk, which makes it a common starting point for fake accounts, promotion abuse and bonus abuse. Teams typically apply validation in three places:

1. At the form field. Catch syntax errors and dead domains before submission, so genuine customers fix typos and your list stays clean.
2. At account creation. Flag disposable domains and apply your policy: block, require extra verification, or limit what a new account can do until it is confirmed.
3. At the decision step. Pass the email result into your rules alongside other signals such as IP and device intelligence, so a single weak signal does not decide the outcome alone. Risk decisioning explains how those rules are structured.

A practical point many guides skip: avoid a blanket block on everything flagged. Role accounts and some privacy-focused addresses are legitimate for real customers, so tune the response to the risk of the action. A newsletter sign-up can tolerate far more than a payout request.

How email and phone signals are combined into a single score is covered separately in Email and Phone Risk Scoring Explained. For checking numbers rather than addresses, see the Free Phone Number Validator, or the Phone Validate product.

Limits: a valid email is not proof of identity

A clean result means the address is well formed, its domain can receive mail and it does not match a known disposable provider. It does not mean the address is active for that mailbox, that it belongs to the person using it, or that the person is who they claim to be. Anyone can register a real address in any name.

Also note that some mail servers accept all mail regardless of whether a specific mailbox exists, so a pass cannot guarantee delivery. For regulated products, treat email validation as a fraud and data-quality control, and use identity verification for identity checks.

Use the Email Validate API at sign-up

For more than the occasional manual check, call the API from your sign-up flow, so every address is checked as it is entered. You can sign up self-serve and test with your own traffic; see pricing for plans. The email check also sits within the wider fraud detection and compliance product and the fraud detection hub.

The response below is an illustration of the kind of result you can expect. Field names and values are examples only, so check the documentation for the exact format.

{
  "email": "jane.doe@example.com",
  "syntax_valid": true,
  "domain_has_mx": true,
  "disposable": false,
  "role_account": false,
  "risk": "low"
}

Validate emails at sign-up with the Email Validate API, or read the product page for details.