Email checker
Check an email address for format errors, mail records, disposable providers, and common domain typos. See the individual checks behind the result, including whether the address is a shared role such as info@ or sales@.
Format and domain checks only. This does not verify that the mailbox exists.
What the email checks mean
The result separates problems with the address from labels that describe the kind of mailbox.
- Format
- Whether the input has a valid email-address structure.
- Mail records
- Whether the domain has the mail setup checked by the service. An unavailable lookup remains unknown.
- Disposable
- Whether the provider is recognized as a temporary email service.
- Role address
- Whether the name describes a shared function, such as support@. This does not make an address invalid.
- Typo suggestion
- A possible correction for a commonly misspelled domain. Confirm it before replacing the address.
Does a passing result mean the mailbox exists?
A passing format and domain check does not establish that the individual mailbox exists or accepts messages. Mailbox verification is a separate operation, and that result can also be unknown.
Use this checker to catch address-entry problems. For mailbox verification or a contact file, use the Email API verification operation or Bulk email verification.
Build an email checker
Use the Email lookup for format, mail-domain, disposable, role, and typo information. Display each check so the visitor can see why an address needs attention.
- Trim the address and encode it as a path value.
- Keep false and unknown values distinct.
- Offer didyoumean as a suggestion for the visitor to confirm.
Installation steps are included in each example. Set PARSEAPI_KEY on your server. Swift and Kotlin use an app key restricted to your app ID.
// npm install @parseapi/sdk@1.14.0
import { parseAPI } from '@parseapi/sdk';
// Set PARSEAPI_KEY on your server.
const parse = parseAPI();
const input = 'name@example.com'.trim();
const row = await parse.email(input);
const status = !row.valid ? 'Invalid format'
: row.domain_valid === false ? 'Mail domain check failed'
: row.domain_valid === null ? 'Mail records unavailable'
: row.disposable === true ? 'Disposable address' : 'Format and domain checked';
console.log({ status, email: row.email, domain: row.domain,
domainValid: row.domain_valid, disposable: row.disposable,
role: row.role, freeProvider: row.free ?? null,
suggestion: row.didyoumean ?? null });
// A lookup does not prove that a mailbox exists or accepts mail.
// Mailbox verification is a separate GET /email/verify operation.
How do I check if an email address is valid?
Enter the complete address. The result separates format, domain mail records, and address labels so you can see whether the problem is a typo, an unusable domain, or something else.
Does a valid result prove the email address exists?
No. Format and domain checks do not establish that the individual mailbox exists or accepts messages. Mailbox verification is a separate operation and can also return an unknown result.
Should I replace an address with the typo suggestion?
Ask the person or check the source first. A suggestion identifies a likely domain spelling correction; applying it automatically could change a genuine address.
Are role, free, or disposable addresses invalid?
These labels describe the address. Role addresses such as info@ can be shared; free identifies a consumer provider; disposable identifies a temporary-address provider. Decide which kinds your workflow accepts separately from format validity.
What does unavailable mail-domain information mean?
It means the lookup could not establish that check. Keep it separate from a definite failed check rather than rejecting it as false.
Can I check an email list?
Use Bulk email verification for a file. Review the quote before running mailbox-level checks.