Email Verification API - Validate Email Addresses

Category Identity & Business

Endpoints 2

Key Features 7

Frequently Asked Questions 2

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.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

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.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

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.

Authenticate once

Send your API key with the documented header and keep requests consistent across services.

Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

Operate and monitor

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.

OpenAPI schema

Generate clients or inspect every request and response shape.

Postman collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose 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.

Request parameters

Parameter

emailemails

Response fields

Example Response

emailnormalized_emailresultresult_detailriskconfidencedecisionreasonsverificationverification.syntax_validverification.mx_foundverification.mx_records

Status coverage

HTTP Status Codes

200400401402429

Endpoints

GET /v1/email/verify

Credits: 2Authentication: Authentication required

POST /v1/email/verify/bulk

Credits: 2/itemAuthentication: Authentication required

emails

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign Up for Free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example Request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Syntax Validation

Check email format against RFC 5322 standards instantly.

MX Record Lookup

Verify domain has valid mail exchange servers configured.

Disposable Detection

Flag temporary emails from 186k+ disposable domains.

Role-Based Check

Identify generic addresses like admin@, support@, info@.

Quality Scoring

Get A-F grades with 0-100 quality scores and risk flags.

Bulk Processing

Verify up to 100 emails in a single API request.

DNSBL Reputation

Check domains against Spamhaus, SURBL, and URIBL blacklists.

Example Request

GET /v1/email/verify bash

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/email/[email protected]"

Example Response

200 OK json

{
  "email": "[email protected]",
  "normalized_email": "[email protected]",
  "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": 2
}

Frequently Asked Questions

What does the quality score mean?

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.

Can I verify emails in bulk?

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.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Verify Emails for Free

Start Free View documentation Try the free tool