Email Validator

Overview

An email verification API and email checker for signup forms and CRM imports. Email Validator checks the address format, resolves the domain's MX records, follows the RFC fallback to the domain's A record, flags domains that publish a null MX, and reports whether the domain has SPF and DMARC records. It matches the domain against free, disposable and role-account lists, and returns a normalized address so +tag and Gmail-dot variants collapse to one. Every check runs over DNS, with no SMTP mailbox probe, so a slow mail server never holds up the response. Paid plans add a risk score and a suggested correction for domain typos.

Live Test Email Validator API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

1
2

curl "https://api.apiverve.com/v1/emailvalidator?email=support%40myspace.com" \
  -H "x-api-key: your_api_key_here"

1
2
3
4
5
6
7
8

const res = await fetch('https://api.apiverve.com/v1/emailvalidator?email=support%40myspace.com', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

1
2
3
4
5
6
7
8
9
10

import requests

res = requests.get(
    "https://api.apiverve.com/v1/emailvalidator?email=support%40myspace.com",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/emailvalidator?email=support%40myspace.com", nil)
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

{
  "status": "ok",
  "error": null,
  "data": {
    "email": "support@myspace.com",
    "domain": "myspace.com",
    "username": "support",
    "isRegexValid": true,
    "hasTypo": false,
    "isMxValid": true,
    "isValid": true,
    "isFreeEmail": false,
    "isCompanyEmail": true,
    "isDisposable": false,
    "isRoleAccount": true,
    "mxRecord": "mxa-00ac0e01.gslb.pphosted.com",
    "isNullMx": false,
    "canReceiveMail": true,
    "hasSpf": true,
    "hasDmarc": true,
    "isSubaddressed": false,
    "normalizedEmail": "support@myspace.com",
    "suggestedCorrection": null,
    "mailProvider": "Proofpoint",
    "isSecurityGateway": true,
    "riskScore": 10,
    "riskLevel": "low"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

Start from a template

Working apps built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.

Lead Validator

Score a lead from its email and phone number: throwaway inboxes, typos, VoIP and temporary numbers.

• Next.js
• React

Also uses Phone Number Validator

Deploy to VercelSee the template →

Signup Email Checker

Accept, review or reject an email at signup: catches throwaway inboxes, dead domains, typos and shared inboxes.

• Node.js
• Express

Deploy to VercelSee the template →

Use cases

Signup Abuse Prevention

To stop fake signups, SaaS onboarding flows block temporary addresses by checking disposable flags before creating new trial accounts.

B2B Lead Routing

Sales teams verify company domains against free provider flags to route corporate inquiries directly to account executives.

Mailing List Hygiene

When scrubbing subscriber databases, email marketers filter out missing mail records and invalid syntax to protect sender reputation.

Customer Support Routing

Flag shared inboxes like billing or support addresses during ticket submission to direct automated receipts to named team members instead.

Free Trial Abuse

Store the normalized address at signup so jane+1@gmail.com and j.ane@gmail.com count as one person when a product hands out free trials or credits.

Other ways to use Email Validator

Set up Email Validator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Related

Pages that use this API:

• Block fake signupsGuides
• CodaIntegrations
• Node-REDIntegrations
• Response formatReference

More in Data Validation: