{
"count": 1,
"results": [
{
"kind": "email",
"input": "[email protected]",
"smtpChecked": false,
"smtpStatus": "skipped",
"smtpNote": "SMTP / port-25 mailbox probing is not performed. Outbound port 25 is unreliable or blocked on typical cloud hosting networks, and a banner-less connect would not prove that an inbox exists.",
"checkedAt": "2026-11-20T18:28:29.487136+00:00",
"normalized": "[email protected]",
"validSyntax": true,
"localPart": "jane.doe",
"domain": "gmial.com",
"isRole": false,
"isFreeProvider": false,
"isDisposable": true,
"typoSuggestedDomain": "gmail.com",
"typoSuggestedEmail": "[email protected]",
"hasA": true,
"aRecords": [
"51.79.68.169"
],
"hasMx": false,
"mxRecords": [],
"hasSpf": false,
"spf": null,
"hasDmarc": false,
"dmarc": null,
"dmarcPolicy": null,
"domainExists": true,
"verdict": "risky",
"score": 0,
"reasons": [
"typosquat_listed_as_disposable",
"possible_typo",
"no_mx"
],
"disposableNote": "This domain is on the disposable/throwaway blocklist. When a typo suggestion is also present (e.g. gmial.com → gmail.com), that usually means a typo-squat listed because it impersonates a mailbox provider, not a temporary-mail service."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/15121/email+validation+and+domain+check+api/40349/[email protected]' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Email Validation and Domain Check API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Check an email address or domain: syntax, typo suggestion, MX and A records, SPF, DMARC, disposable, free and role-based detection, with a verdict and score.
Syntax, typo suggestions, MX and A records, SPF, DMARC and its policy, disposable domains, free mailbox providers and role accounts. Each result has a verdict, a score from 0 to 100 and a list of reasons.
No. It does not open an SMTP connection on port 25, so it cannot confirm a single mailbox. It checks everything that can be verified through DNS and domain reputation.
Yes. Send the domain parameter instead of email and you get MX, A, SPF, DMARC and disposable checks for that domain.
Valid means the address passed all checks, risky means it may work but has warning signs such as a typo domain or no MX record, invalid means it cannot receive mail.
Most calls finish in well under one second because only DNS lookups are made. Results are computed live on every call.
Provide either one email address or one domain using the endpoint’s corresponding input parameter. The API identifies the input as `kind: "email"` or `kind: "domain"` and returns checks appropriate to that type. Do not submit both values for the same validation request.
The endpoint returns a JSON object containing `count` and a `results` array. Each result represents the submitted email or domain and includes normalized input, validation findings, DNS data, classification flags, a verdict, and a score.
Email results can include `normalized`, `localPart`, `domain`, `validSyntax`, `isRole`, `isFreeProvider`, `isDisposable`, and typo suggestions such as `typoSuggestedDomain` and `typoSuggestedEmail`. These fields help separate formatting issues from mailbox and domain risks.
`hasA` indicates whether the domain has A records, which appear in `aRecords`. `hasMx` indicates whether mail-exchange records exist, listed in `mxRecords`. An empty `mxRecords` array means no MX records were found, even if the domain has an A record.
SPF and DMARC fields report whether the domain publishes these email-authentication records and expose relevant record or policy details when available. Use them to assess domain-level sending and anti-spoofing configuration alongside MX and A results.
`smtpChecked` and `smtpStatus` show whether mailbox probing was performed. In the example, SMTP is skipped because the API does not use port-25 probing. `smtpNote` explains that a connection would not reliably prove an inbox exists.
Use the score as a numeric risk signal and the verdict as a high-level classification. Combine them with individual fields and reasons: for example, a typo suggestion, disposable flag, missing MX records, or role-account flag can trigger review or correction rather than automatic rejection.
Treat each check independently. A domain may have A records but no MX records, or may lack SPF or DMARC while still resolving. Check boolean fields such as `hasA` and `hasMx`, inspect arrays for empty results, and use the overall verdict with the detailed findings.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund