Disposable Email Checker API - Detect Throwaway and Temporary Addresses
Every signup form collects a share of addresses from throwaway providers, and the accounts behind them look identical to genuine ones until they churn, bounce a receipt, or never open a single email you send. The APIFreaks Disposable Email Checker API flags those addresses in a single REST call. It checks whether the address comes from a known throwaway provider, whether its domain resolves and has mail servers, and whether it is a free-provider, spam-listed, or role-based address. Add the signup IP and the same call also returns its location and fraud and spam signals.
It's built for developers and growth teams keeping throwaway signups out of free trials, referral programs, and contact forms, one address at a time or up to 100 per request. Start with 10,000 free credits, no credit card required.
Features
Throwaway Address Flagging
Addresses from known throwaway and temp-mail providers come back with domain.disposable set to true. It's the core signal this API exists for.
Use it as your primary gate: reject or flag disposable addresses at the point of signup, before a burner account ever gets created.
Format Check
Every response includes validSyntax, so malformed addresses are easy to reject on the spot. A malformed address still gets a normal response, with domain.validDomain set to false.
Use it to catch typos at the form, before the address goes anywhere else in your flow.
Free Provider and Spam List Flags
Two separate flags describe the domain itself: domain.free marks consumer providers like Gmail or Outlook, and domain.spam marks domains already listed in spam databases.
Use these together when a form needs to separate personal addresses from business ones, or keep spam-listed domains out entirely.
Shared Inbox Flagging
Inboxes like support@, read by a team rather than a person, are marked in account.role.
Use it to keep team inboxes out of individual user accounts, where the signup needs a personal address.
DNS and Mail Server Data
Each response reports whether the domain resolves and is set up for mail (domain.validDomain), and lists the mail servers in its MX records (dns.mxRecord) and its A records (dns.aRecord) where it has them.
Use validDomain to reject addresses on domains that don't exist. Keep mxRecord with the signups you flag, so a reviewer can see where the mail goes.
IP Location and Fraud Detection
Pass an optional ip with the address and the result comes back with an address object: the connection's location (address.location), plus fraud and spammer flags in address.security such as proxy, Tor, bot, known attacker, and spam, along with a threat_score. IP data doesn't cost any extra credits.
Use it to see where a signup came from and whether the connection behind it looks like fraud or spam, alongside the disposable flag.
Bulk Checks for Existing Lists
Up to 100 addresses can go in one request, each with an optional IP of its own, and each one gets its own result, so a malformed address never fails the batch.
Use it to sweep an existing list for disposable and role-based addresses before you import it.
Built for These Use Cases
Free-trial and signup abuse
Check the address as it's entered and reject or flag throwaway domains and shared team inboxes before the account is created. The same check works on forums and community platforms, where a disposable address is often how someone gets around a ban.
Signups from proxies and anonymizing networks
Send the signup IP with the email and flag accounts created through proxies or Tor, or from regions you don't serve. A disposable address arriving through an anonymized connection deserves a closer look than either signal on its own.
Referral and promo abuse prevention
Screen the email behind a referral claim or promo redemption. A burst of disposable addresses redeeming the same offer is a common sign the program is being farmed rather than shared.
Contact form and demo request filtering
Check addresses submitted through demo requests and contact forms, and keep throwaway and role-based entries out of your sales pipeline. Pair the free-provider flag with your own rules when only company addresses should reach the CRM.
Cleaning a list before import
Run a list through the bulk endpoint before it goes into your CRM or mailing platform, so throwaway and role-based addresses never reach your database.
API Endpoint
How-To-Guides
Check a Single Address at Signup
Send the address to the single-check endpoint before the account is created.
curl -X POST \
'https://api.apifreaks.com/v2.0/email/disposable-check?apiKey=API-KEY' \
-H 'Content-Type: application/json' \
-d '{
"email": "john@1000gmail.com"
}'
# Response
{
"email": "john@1000gmail.com",
"validSyntax": true,
"domain": {
"disposable": true,
"free": false,
"name": "1000gmail.com",
"spam": false,
"validDomain": true
},
"account": {
"role": false
},
"dns": {
"mxRecord": [
"srv4.recoverhost.com.",
"em4.recoverhost.com."
]
}
}
1000gmail.com returns disposable: true despite its Gmail-style name.
Add the Signup IP to a Check
Send the signup IP with the address to get the connection's location and fraud and spam signals back in the same call.
curl -X POST \
'https://api.apifreaks.com/v2.0/email/disposable-check?apiKey=API-KEY' \
-H 'Content-Type: application/json' \
-d '{
"email": "john@1000gmail.com",
"ip": "8.8.8.8"
}'
# Response
{
"email": "john@1000gmail.com",
"validSyntax": true,
"domain": {
"disposable": true,
"free": false,
"name": "1000gmail.com",
"spam": false,
"validDomain": true
},
"account": {
"role": false
},
"dns": {
"mxRecord": [
"srv4.recoverhost.com.",
"em4.recoverhost.com."
]
},
"ip": "8.8.8.8",
"address": {
"location": {
"city": "Mountain View",
"continent_code": "NA",
"continent_name": "North America",
"country_code2": "US",
"country_code3": "USA",
"country_name": "United States",
"country_name_official": "United States of America",
"district": "Santa Clara",
An invalid or reserved IP still returns a 200, with address.validIpAddress set to false.
Screen an Existing List in Bulk
Send up to 100 addresses to the /bulk path in one call, each with an optional IP.
curl -X POST \
'https://api.apifreaks.com/v2.0/email/disposable-check/bulk?apiKey=API-KEY' \
-H 'Content-Type: application/json' \
-d '{
"emailData": [
{ "email": "abc" },
{ "email": "john@microsoft.com", "ip": "8.8.8.8" }
]
}'
# Response
{
"disposableEmailResponse": [
{
"email": "abc",
"validSyntax": false,
"domain": {
"name": "abc",
"validDomain": false
}
},
{
"email": "john@microsoft.com",
"validSyntax": true,
"domain": {
"disposable": false,
"free": false,
"name": "microsoft.com",
"spam": false,
"validDomain": true
},
"account": {
"role": false
},
"dns": {
"mxRecord": [
"microsoft-com.mail.protection.outlook.com."
]
},
"ip": "8.8.8.8",
"address": {
Each entry gets its own result, with ip and address returned only for the entries where you sent an IP.
Frequently Asked Questions
domain.disposable in the response. true means the address comes from a known throwaway or temp-mail provider.domain.validDomain) and lists its MX and A records, so addresses on domains that don't exist or aren't set up for mail are easy to catch.emailData in a POST request to the /bulk path, each with an email and an optional ip. Each entry gets its own result. Make sure every entry has an email, since a request with a null entry or an entry without one is rejected with a 400.200, and address.validIpAddress is false. If the IP lookup itself fails, address is left out and the disposable result isn't affected.domain.free marks consumer providers and domain.disposable marks throwaway ones. They're independent flags, so you can block one and allow the other.Pricing
To use the Disposable Email Checker API, you will need API credits. We only charge for successful queries, defined by a 2xx status code. If your request results in a 4xx or 5xx status code, no credits will be charged, and any deducted credits will be returned.
For each email address checked, 15 credits are charged.
Utilize the Credits Usage API to efficiently monitor your recent consumption of both one-off and subscription credits. This API provides a streamlined way to track and manage your credit usage, ensuring you stay informed about your remaining balance and can optimize your resource allocation effectively.