Introduction

The Email Validation API is a REST service that verifies email addresses in real time: syntax, DNS (MX / A records), SMTP deliverability, disposable domains, role-based addresses, and typo suggestions — all in a single HTTP call.

Why an email validation API?

• Clean your signup forms — block fake, misspelled, or disposable addresses before they hit your database.
• Verify mailing lists — reduce bounces before sending campaigns.
• Prevent abuse — flag suspicious patterns (role-based, disposable domains, anti-probe providers).

Base URL

https://email-validation-api.net/api/v1

What we check

• Syntax — RFC 5322 compliance
• MX / A records — can the domain receive mail?
• SMTP (RCPT TO) — does the mailbox exist? (enabled by default)
• Disposable — blocks mailinator, yopmail, tempmail, 10minutemail, etc.
• Role-based — detects info@, contact@, admin@, support@…
• Typo detection — Levenshtein distance against popular domains

First request

curl https://email-validation-api.net/api/v1/validate \
  -H "Authorization: Bearer evs_live_XXXX..." \
  -H "Content-Type: application/json" \
  -d '{"email":"user@example.com"}'

Example response:

{
  "email": "user@example.com",
  "valid": true,
  "reason": "ok",
  "confidence": "verified",
  "score": 1.0,
  "details": {
    "syntax": true,
    "domain": "example.com",
    "mx": true,
    "mx_records": ["mail.example.com"],
    "disposable": false,
    "role_based": false,
    "smtp": true
  },
  "credits_remaining": 99940,
  "cached": false
}

The confidence field

• "verified" — the remote SMTP server confirmed the mailbox exists (RCPT TO returned 250).
• "basic" — syntax + DNS OK but SMTP could not confirm (anti-probe provider like Proton/Tutanota, catch-all server, or server unreachable).

For critical signup forms, require confidence === "verified". For simple anti-typo filtering, valid === true is enough.

About latency

Every validation runs the full pipeline : syntax, MX, disposable, role-based, typo detection, and — when the provider allows it — SMTP RCPT TO probe. Typical latency is 80-400ms thanks to intelligent caching (same email revalidated within 1h : <10ms). For very large lists use the async endpoint to avoid HTTP timeouts.