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
Stop fake and mistyped emails before they reach your list.
Email Validator is an email validation API that checks whether an address is well-formed, whether its domain can receive mail, and whether it is safe to accept. It validates the format, resolves MX records (including null MX and the A-record fallback), checks for SPF and DMARC, flags disposable, role and free-provider addresses, and returns a normalized address for spotting duplicates. Paid plans add a risk score and typo correction.
No key required to try it. Get a key to use it in your app.
{
"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,
"riskScore": 10,
"riskLevel": "low"
}
}
Score a lead from its email and phone number: throwaway inboxes, typos, VoIP and temporary numbers.
Also uses Phone Number Validator
Accept, review or reject an email at signup: catches throwaway inboxes, dead domains, typos and shared inboxes.
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.
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
Side by side with the tools people weigh Email Validator against — what each one is better at, in plain terms.
Same data, same APIVerve account, same credit balance — one key works on all of them.
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
| Parameter | Type | Example | Description |
|---|---|---|---|
emailRequired | string | support@myspace.com | The email address to validate (e.g., support@myspace.com) email |
curl "https://api.apiverve.com/v1/emailvalidator?email=support%40myspace.com" \
-H "x-api-key: YOUR_API_KEY"Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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,
"riskScore": 10,
"riskLevel": "low"
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
email | string | "support@myspace.com" | The email address that was validated |
domain | string | "myspace.com" | The domain portion extracted from the email |
username | string | "support" | The username (local part) extracted from the email |
isRegexValid | boolean | true | Email passes standard regex format validation |
hasTypo | boolean | false | The address is malformed and fails format validation |
isMxValid | boolean | true | The domain has valid mail exchange (MX) records and can receive mail |
isValid | boolean | true | Indicates whether the email address is valid |
isFreeEmail | boolean | false | Domain belongs to a free consumer email provider |
isCompanyEmail | boolean | true | Domain appears to be a corporate/company domain |
isDisposable | boolean | false | Domain is a known disposable or throwaway email provider |
isRoleAccount | boolean | true | Mailbox is a role or shared address (e.g. info@, support@, noreply@) rather than a person |
mxRecord | string | "mxa-00ac0e01.gslb.pphosted.com" | The preferred (lowest-priority) mail exchanger host for the domain, or null when it has none |
isNullMx | boolean | false | The domain publishes a null MX record (RFC 7505), declaring that it accepts no email |
canReceiveMail | boolean | true | The domain can be sent mail: it has a real MX record, or no MX at all but an A record that mail falls back to (RFC 5321). Null if the fallback lookup could not complete. Unlike isMxValid, this follows the RFC fallback, so a parked domain with only a website address can be true |
hasSpf | boolean | true | The domain publishes an SPF (v=spf1) record, a sign it is set up to send mail. Null if the TXT lookup could not complete |
hasDmarc | boolean | true | The domain publishes a DMARC (v=DMARC1) record at _dmarc. Null if the lookup could not complete |
isSubaddressed | boolean | false | The address uses a +tag sub-address, e.g. jane+news@example.com |
normalizedEmail | string | "support@myspace.com" | Canonical address for spotting duplicates: the +tag removed, and for Gmail the dots too (googlemail.com folds into gmail.com). Not a deliverability claim |
suggestedCorrectionPremium | object | null | The likely intended email when a common domain typo is detected (e.g. gmial.com to gmail.com), otherwise null |
riskScorePremium | number | 10 | Composite 0-100 risk score combining deliverability, disposable, role and format signals (higher is riskier) |
riskLevelPremium | string | "low" | Risk band derived from the score: low, medium or high |
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Email Validator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 10 | Free |
| Starter | $29.99 | 200,000 | 10,000 | $3.00 |
| Pro | $99.99 | 1,000,000 | 50,000 | $2.00 |
| Mega | $299.99 | 4,000,000 | 200,000 | $1.50 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
No SDK to install — this is a plain HTTPS call to /v1/emailvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/emailvalidator" \
-H "x-api-key: YOUR_API_KEY"Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Node.js SDK, then call the Email Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/emailvalidatorconst res = await fetch("https://api.apiverve.com/v1/emailvalidator", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Python SDK, then call the Email Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-emailvalidatorimport requests
res = requests.get(
"https://api.apiverve.com/v1/emailvalidator",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the C# / .NET SDK, then call the Email Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.EmailValidatorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/emailvalidator");
Console.WriteLine(json);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/emailvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/emailvalidator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/emailvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/emailvalidator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/emailvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/emailvalidator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyOnly the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Drop an interactive Email Validator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Email Validator API.
Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read
Email Validation Best Practices: Beyond Simple RegexEmail validation beyond regex. Learn how to verify deliverability without rejecting legitimate users.Read
Email Deliverability is Not Your Email Server's ProblemYour email server works perfectly but emails go to spam. Here's why IP reputation matters and how to avoid blacklists.Read