Registration & forms
Catch invalid address formats and flag disposable-domain signals during account or contact intake.
EMAIL VALIDATION API
Email validation
and risk signals.
Check the mail service, SMTP recipient response, disposable-domain status and spam-list signals behind an email address. Return the individual checks to your application.
2 credits / checkEmail address inJSON response out
EXAMPLE RESULTSEMAIL VALIDATION
VALID
The mail server accepted the recipient check.
- Address format
- Valid
- Mail service
- Found
- SMTP recipient
- Accepted
- Disposable / spam-listed
- No / No
UNKNOWN
The server did not give a conclusive recipient result.
- Address format
- Valid
- Mail service
- Found
- SMTP recipient
null- Account status
unknown
{
"verdict": "VALID",
"account_status": "accepted",
"checks": {
"format": true,
"service": true,
"account": true,
"disposable": false,
"spam": false
}
}Illustrative response excerpts · reserved example.com address
EMAIL VALIDATION USE CASES
Validate addresses
in your application.
Bring structured address validation into the workflows that collect, review and maintain contact information.
Contact data quality
Use mail-service and recipient results to identify entries that need correction or confirmation.
Review & investigation
Attach the individual checks to a case so your team can see why an address was flagged.
READ THE RESULT
Validation outcomes
and individual checks.
Keep the overall verdict and individual checks together. A recipient rejection and an incomplete check are different outcomes.
| Verdict | What it means | How to use it |
|---|---|---|
VALID | The SMTP server accepted the recipient check, with no returned disposable or spam-list flags. | Continue your address-confirmation workflow. |
INVALID | The address format is invalid. | Ask for a correction. |
NON_EXISTENT | Mail-service validation failed or the recipient was definitively rejected. | Review or correct the address. |
RISKY | Disposable-domain or spam-list signals were found. | Apply the appropriate review policy. |
UNKNOWN | The recipient check was inconclusive. | Use confirmation or a later recheck. |
This API validates an address, not the contents of an email message. Use a confirmation email to establish ownership; SMTP acceptance is not a delivery guarantee.
START BUILDING
Integrate the
Email Validation API.
Send an email address from your backend and map the JSON result to the validation rules in your application.
2 credits / successful checkCompare API plans
Completed checks, including inconclusive results, use credits.
POST /api/v1/email/check
curl -X POST 'https://inspector.gridinsoft.com/api/v1/email/check' \
-H 'Content-Type: application/json' \
-d '{
"apikey": "YOUR_PRIVATE_APIKEY",
"email": "[email protected]"
}'One address per request. See the documentation for fields and error handling.
API licensing & data handling
API subscriptions use our standard terms. Paying for a plan does not make submissions private or remove our rights to use and publish analysis. Private processing, customer-facing services, redistribution, and other special rights require written agreement. Discuss your requirements.