Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Used by people at amazing companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Send your API key with the documented header and keep requests consistent across services.
Start from the curl and HTTP samples, then map the parameters into your application code.
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
Example Response
HTTP Status Codes
Endpoints
/v1/email/verify
/v1/email/verify/bulk
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Check email format against RFC 5322 standards instantly.
Verify domain has valid mail exchange servers configured.
Flag temporary emails from 186k+ disposable domains.
Identify generic addresses like admin@, support@, info@.
Get A-F grades with 0-100 quality scores and risk flags.
Verify up to 100 emails in a single API request.
Check domains against Spamhaus, SURBL, and URIBL blacklists.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/email/verify?email=user@company.com"
Example Response
{
"email": "user@company.com",
"normalized_email": "user@company.com",
"result": "valid",
"result_detail": "mx_verified",
"risk": "low",
"confidence": 0.62,
"decision": "accept",
"reasons": ["mx_found", "not_disposable", "mailbox_not_checked", "redundant_mx_records"],
"verification": {
"syntax_valid": true,
"mx_found": true,
"mx_records": ["mx1.company.com", "mx2.company.com"],
"smtp_verified": null,
"mailbox_exists": null,
"catch_all": null
},
"classification": {
"disposable": false,
"role_based": false,
"free_provider": false,
"provider": null
},
"reputation": {
"dnsbl_listed": false,
"threat_level": null
},
"quality": {
"score": 100,
"grade": "A",
"flags": []
},
"signals": {
"domain_profile": { "status": "pass", "reason": "clean_domain_profile" },
"local_part": { "status": "pass", "reason": "clean_local_part" },
"mx_redundancy": { "status": "pass", "reason": "redundant_mx_records" },
"domain_authentication": { "status": "pass", "reason": "domain_authentication_strong" },
"toxicity": { "status": "pass", "reason": "not_toxic" }
},
"recommendation": {
"signup": "allow",
"marketing": "send",
"cold_outreach": "send"
},
"deliverability": {
"status": "deliverable",
"sub_status": "mx_verified",
"safe_to_send": true,
"is_toxic": false,
"is_gibberish": false
},
"tier": "basic",
"credits_used": 1
}
Frequently Asked Questions
The quality score (0-100) reflects email deliverability risk. Grade A (90-100) is excellent, B (75-89) is good, C (60-74) is moderate risk, D (40-59) is high risk, and F (0-39) indicates invalid or very risky addresses.
Yes! Use the /v1/email/verify/bulk endpoint to verify up to 100 emails in a single request. Results include individual verification details plus summary statistics.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
Request successful
Invalid parameters
Not enough credits to run this request.
Rate limit exceeded
Internal error
Upstream RDAP error
Upstream service unavailable or temporarily rate limited.
Upstream lookup timed out.
Verify Emails for Free