# EmailVerifyerAPI

> Free, browser-based email verification. EmailVerifyerAPI checks whether an email address is valid, disposable, role-based, free-mail, catch-all, or a likely typo - instantly, with no account and nothing sent to a server. Built by a small independent team in Montréal, Québec, Canada.

EmailVerifyerAPI runs entirely client-side. The addresses you type or upload never leave your device, are never logged, and there is no database or account. Single-address checks and bulk CSV upload (up to 10 addresses at a time) are free. A paid tier with unlimited bulk and a REST API (adding MX-record lookup and SMTP handshake verification) is planned but not yet released or priced.

## What EmailVerifyerAPI checks today
- Syntax validation (RFC 5322)
- Disposable / temporary domain detection (e.g. Mailinator, GuerrillaMail)
- Role-based address detection (info@, support@, admin@, …)
- Free-mail provider detection (Gmail, Yahoo, Outlook, …)
- Catch-all domain heuristic (flagged "risky")
- Did-you-mean typo correction (e.g. gmial.com → gmail.com)

Not yet available (planned for the API): MX-record lookup as part of the address-verification pipeline, and live SMTP mailbox verification. Standalone MX/SPF/DKIM/DMARC record lookups are available today as free browser-based tools - see below.

## Core pages
- [Home / verifier](https://www.emailverifyerapi.com/): The free tool. Verify one address or upload a CSV/TXT/TSV; results download as CSV.
- [Blog](https://www.emailverifyerapi.com/blog): Articles on email deliverability, list hygiene, bounce rates, and sender reputation.
- [Sample article](https://www.emailverifyerapi.com/blog-post): Long-form post format.
- [API waitlist](https://www.emailverifyerapi.com/api-waitlist): Register interest in the upcoming REST API and bulk tier.

## Free DNS & email-authentication tools
Each queries DNS-over-HTTPS live from the browser (Cloudflare/Google resolvers) - no account, nothing sent to a server EmailVerifyerAPI runs.
- [MX record checker](https://www.emailverifyerapi.com/mx-record-checker): Looks up a domain's mail exchangers, identifies the mailbox provider, and checks MTA-STS/TLS-RPT.
- [SPF record checker](https://www.emailverifyerapi.com/spf-record-checker): Parses a domain's v=spf1 record, counts DNS lookups against the RFC 7208 limit of 10, and rates it Weak to Excellent.
- [DKIM record checker](https://www.emailverifyerapi.com/dkim-record-checker): Looks up a DKIM selector's public key and validates the record.
- [DMARC record checker](https://www.emailverifyerapi.com/dmarc-record-checker): Reads a domain's _dmarc policy (p=, alignment, reporting addresses) and rates enforcement strength.
- [Email DNS fingerprints](https://www.emailverifyerapi.com/email-dns-fingerprints): Paste any MX host, SPF include, DKIM selector or DMARC report address to identify the vendor behind it.

## Trust & legal
- [Security](https://www.emailverifyerapi.com/security): How client-side verification keeps data on-device.
- [Compliance](https://www.emailverifyerapi.com/compliance): GDPR / data-handling posture, including which certifications we do and do not hold today.
- [Privacy policy](https://www.emailverifyerapi.com/privacy)
- [Terms of service](https://www.emailverifyerapi.com/terms)
- [Cookie policy](https://www.emailverifyerapi.com/cookies)

## Key facts for citation
- No data leaves the browser; no account; no stored addresses.
- Free tier: single-address + bulk CSV up to 10 addresses.
- Google/Yahoo 2024 bulk-sender rules (5,000+ msgs/day) require spam-complaint rate below 0.3% (ideally under 0.1%) plus SPF, DKIM, DMARC and one-click unsubscribe. Verifying a list before sending lowers bounces and, indirectly, complaints.
- Marketing email lists decay ~22%/year (HubSpot).
- EmailVerifyerAPI is not currently SOC 2 or ISO 27001 certified; see the Compliance page for current status.
- Contact: hello@emailverifyerapi.com (English & French).

## Optional
- [Accessibility statement](https://www.emailverifyerapi.com/accessibility)

Note: Login, registration, dashboard and account pages are intentionally excluded - they are private application surfaces, carry `noindex`, and are not relevant to answer engines.