Email Blacklist API - Disposable Email Detection

Category Security

Endpoints 4

Key Features 8

Frequently Asked Questions 5

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.

99.99% Uptime

Production-ready endpoints are designed for 99.99% uptime and documented status handling.

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

emailtargetsformat

Response fields

Example Response

emaildomainlocal_partvalid_syntaxcheckschecks.disposablechecks.disposable.is_disposablechecks.disposable.confidencechecks.rolechecks.role.is_rolechecks.role.role_typechecks.free

Status coverage

HTTP Status Codes

200400402429500502503504

Endpoints

GET /v1/email/check

Credits: 1Authentication: optional

POST /v1/email/check/bulk

Credits: 1Authentication: optional

targets

GET /v1/email/blacklist

Credits: 0Authentication: optional

GET /v1/email/blacklist/download

Credits: 0Authentication: optional

format

Trust signals before you integrate

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

Uptime 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

186K+ Disposable Domains

Comprehensive database aggregated from 5 open-source repositories, updated daily.

Confidence Scoring

High, medium, and low confidence levels based on cross-source verification.

Role-Based Detection

Identify admin@, support@, info@ and other role-based addresses.

Free Provider Detection

Flag Gmail, Yahoo, Outlook, and other free email providers.

MX Record Validation

Verify the domain can actually receive email.

DNSBL Check

Check domain against Spamhaus, SURBL, and URIBL blacklists.

Risk Scoring

Aggregate risk score 0-100 with low/medium/high classification.

Bulk API

Check up to 100 emails in a single API request with summary stats.

Example Request

GET /v1/email/check bash

Open

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/email/check?email=user@10minutemail.com"

Example Response

200 OK json

{
  "email": "user@10minutemail.com",
  "domain": "10minutemail.com",
  "local_part": "user",
  "valid_syntax": true,
  "checks": {
    "disposable": { "is_disposable": true, "confidence": "high" },
    "role": { "is_role": false, "role_type": null },
    "free": { "is_free": false, "provider": null },
    "mx": { "has_mx": true, "records": ["mx1.10minutemail.com"] },
    "dnsbl": { "listed": false, "lists": [], "threat_level": "none" }
  },
  "risk_score": 80,
  "risk_level": "high",
  "flags": ["DISPOSABLE_DOMAIN"],
  "checked_at": "2026-03-29T18:00:00.000Z"
}

Frequently Asked Questions

What is a disposable email?

Disposable emails (also called temporary, burner, or throwaway emails) are addresses that self-destruct after a short time. Services like 10minutemail, guerrillamail, and tempmail are commonly used to bypass signup verification.

Why should I block disposable emails?

Users with disposable emails have near-zero engagement and often abuse your service. Blocking them improves signup quality, reduces fake accounts, and saves costs on email sending.

How often is the blacklist updated?

Our database updates daily. Access the full list via GET /v1/email/blacklist.

Can I access the full blacklist?

Yes! Use GET /v1/email/blacklist to get the paginated feed with up to 10,000 domains per request. Include offset and limit parameters to page through the full list.

What is the risk score based on?

Disposable domain (+80), no MX records (+50), DNSBL listed (+60), role-based address (+20), free provider (+10). Scores are capped at 100 and classified as low (0-39), medium (40-69), or high (70-100).

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

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Server Error 500

Internal error

Bad Gateway 502

Upstream RDAP error

Service Unavailable 503

Upstream service unavailable or temporarily rate limited.

Gateway Timeout 504

Upstream lookup timed out.

Start Blocking Disposable Emails

View Full API Documentation APIs