Disposable Email Shield
Real-time verification to block burner/temporary email domains. Protect signups from fake accounts.
/api/verify
Overview
The Disposable Email Shield API provides real-time verification to identify and block temporary, burner, and disposable email addresses. Protect your platform from fake registrations, spam, and abuse by validating email addresses against a comprehensive database of known disposable email providers.
With over 500+ disposable domains in our blocklist and intelligent subdomain matching, this API ensures that only legitimate email addresses can access your services. Automatic DNS MX record validation adds an extra layer of verification to confirm that the email domain can actually receive messages.
Key Features
- 500+ Domain Blocklist — Comprehensive database of known disposable email providers
- Subdomain Matching — Detects disposable emails on subdomains (e.g., temp.gmail.com)
- DNS MX Validation — Automatic verification that the domain has valid mail servers
- AOT-Safe Regex — Compiled regex patterns for lightning-fast validation
- Sub-50ms Response — Near-instant verification for real-time protection
Code Example
curl -X POST https://api.atomicapis.dev/api/verify \
-H "X-RapidAPI-Proxy-Secret: YOUR_SECRET" \
-H "Content-Type: application/json" \
-d '{
"email": "[email protected]"
}'
const response = await fetch('https://api.atomicapis.dev/api/verify', {
method: 'POST',
headers: {
'X-RapidAPI-Proxy-Secret': 'YOUR_SECRET',
'Content-Type': 'application/json'
},
body: JSON.stringify({
email: '[email protected]'
})
});
const result = await response.json();
console.log(result);
import requests
response = requests.post(
'https://api.atomicapis.dev/api/verify',
headers={
'X-RapidAPI-Proxy-Secret': 'YOUR_SECRET',
'Content-Type': 'application/json'
},
json={
'email': '[email protected]'
}
)
result = response.json()
print(result)
using System.Net.Http.Json;
var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-RapidAPI-Proxy-Secret", "YOUR_SECRET");
var request = new
{
email = "[email protected]"
};
var response = await client.PostAsJsonAsync(
"https://api.atomicapis.dev/api/verify",
request
);
var result = await response.Content.ReadFromJsonAsync<VerifyResponse>();
Console.WriteLine(result);
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
email |
string | Required | Email address to verify (max 254 characters) |
Response Schema
{
"email": "[email protected]",
"domain": "tempmail.com",
"isDisposable": true,
"hasMxRecords": null,
"verdict": "disposable"
}
| Field | Type | Description |
|---|---|---|
email |
string | The email address that was verified |
domain |
string | null | The extracted domain from the email address (null if email format is invalid) |
isDisposable |
boolean | True if the email is from a disposable domain |
hasMxRecords |
boolean | null | Whether the domain has valid MX records (null when skipped, e.g. disposable domains or DNS errors) |
verdict |
string | Verdict: "valid", "disposable", "no_mx_records", "dns_error", or "invalid_format" |
Use Cases
User Registration Protection
Block fake accounts at the point of registration. Prevent users from signing up with temporary emails to claim multiple free trials or abuse promotional offers.
Form Spam Prevention
Protect contact forms, newsletter signups, and lead generation forms from spam submissions using disposable email addresses that clutter your database.
Email List Cleaning
Validate existing email lists to remove disposable addresses before campaigns. Improve deliverability rates and reduce bounce rates.
Build Constraints
Technical Implementation
The Disposable Email Shield is built with performance and reliability at its core. Here are the key technical constraints and implementation details:
-
Embedded 500+ Domain List
The blocklist is compiled directly into the binary for zero-dependency operation. No external database calls required for domain lookups.
-
Subdomain Matching
Intelligent pattern matching detects disposable emails on subdomains (e.g.,
[email protected]) using trie-based lookups. -
DNS MX Validation
Automatic MX record lookup validates that the domain can receive email. Performed for all non-disposable, valid-format emails.
-
AOT-Safe Regex
All regex patterns are Ahead-of-Time compiled for maximum performance. No runtime regex compilation overhead.
Error Codes
| Code | Status | Description |
|---|---|---|
400 |
Bad Request | Missing or empty email field (note: an invalid email format returns 200 with verdict invalid_format) |
401 |
Unauthorized | Invalid or missing API key |
429 |
Too Many Requests | Rate limit exceeded |
500 |
Internal Error | Server error - contact support |
MCP Integration MCP Ready
What is MCP?
Model Context Protocol (MCP) allows AI assistants like Claude to call this API as a native tool during conversation. Instead of writing HTTP requests, the AI invokes the tool directly — no API keys or boilerplate needed on the client side.
Tool Details
EmailShieldTools
VerifyEmail()
Description
Checks if an email address is disposable or from a burner domain