Free Disposable Email Checker: Detect Throwaway Addresses

Check if any email address comes from a disposable, temporary, or throwaway provider. Spot fake signups, free-trial abuse, and low-intent leads before they hit your database.
Enter an email address to start
Need inspiration? Try
Try
test@abstractapi.com
Check catch-all status
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Learn more about the free Email Verifier
Checking
5
Results for
email
Disposable email:
TEST
Deliverability:
TEST
Free email:
TEST
Valid format:
TEST
Valid SMTP:
TEST
Valid MX record:
TEST
Get free credits, more data, and faster results

What is a disposable email checker?

A disposable email checker tells you whether an email address comes from a temporary inbox provider. Services like Mailinator, Guerrilla Mail, 10MinuteMail, and Temp-Mail give users an inbox they can read for minutes or hours, then discard. The address looks like a normal email but routes to a provider known for hosting throwaway accounts.

The check is domain-based. Everything after the @ is matched against a list of known disposable providers. Abstract maintains a list of 8M+ disposable domains, updated daily as new throwaway services launch. If the domain matches, the address is flagged as disposable.

Disposable detection is one signal in a larger trust picture. It will not catch every fake signup, and a small share of legitimate users do use disposable addresses for privacy. Treat the result as a risk input, not a binary verdict.

How disposable email detection works

When you submit an address, the lookup runs three steps:

  1. Domain extraction. The tool splits the address at the @ and isolates the domain. The username (the part before the @) is ignored because disposable detection works at the domain level.
  2. List match. The domain is checked against Abstract's list of 8M+ known disposable providers. The list includes large public services (Mailinator, 10MinuteMail) and the long tail of smaller throwaway sites that operators use to evade simple blocklists.
  3. Response. The result returns a single boolean for is_disposable, plus related quality signals: is_free_email (Gmail, Yahoo, Outlook), is_role (info@, support@, admin@), is_catchall (the domain accepts mail for any address), and a 0-to-1 quality score that combines them.

The list updates daily because new disposable providers launch every week. A stale list misses recent operators, which is why detection accuracy is essentially a measure of how fresh the underlying data is.

How to read the result

The primary field is is_disposable. True means the domain is a known disposable provider. False means it is not on the list, but it does not guarantee the address is legitimate.

Three related fields sharpen the signal.

is_free_email flags consumer mailboxes (Gmail, Yahoo, Outlook). These are not disposable, but a B2B signup using a free email may indicate a personal account on a shared corporate trial, or a contractor without a company address.

is_role flags addresses like info@, support@, or sales@. These are real mailboxes but rarely belong to a single buyer. Sending personalized outreach to a role address typically wastes the touch.

is_catchall flags domains that accept mail for any local-part. Catchall domains complicate verification because SMTP confirms every address as deliverable, even ones that don't exist. They are not disposable, but they reduce confidence in deliverability scoring.

The quality score combines these signals into a 0-to-1 number. Use it as a single threshold for filtering, or use the individual booleans to build custom rules per use case.

Use cases for disposable email detection

Signup form filtering: The most common use. Block or flag disposable signups at account creation to keep them out of your user table. For products with free trials, refundable purchases, or generous free tiers, disposable signups can represent a meaningful share of total signups and produce zero conversion. Pair the disposable check with email format validation and deliverability scoring for a complete signup gate.

Email list hygiene: Run existing contact lists through disposable detection before campaigns. Disposable addresses are abandoned within hours, so sending to them produces hard bounces, drags down sender reputation, and inflates list size without adding reachable users. List hygiene is especially valuable before re-engagement campaigns, since old lists accumulate disposables from years of signups.

Fraud and abuse prevention: Disposable email is a common pattern in coordinated abuse: trial farming, fake review generation, promo code stacking, fake account creation. On its own, the disposable signal is not enough to block; on its own, almost no fraud signal is. Combine disposable detection with IP risk scoring, domain age, and behavioral signals to flag suspicious cohorts without false-positiving real users.

Sales lead qualification: For B2B teams qualifying inbound leads, disposable addresses are usually low-intent. Real buyers with budget rarely use throwaway emails. Routing disposable signups through a different qualification flow (lower priority, automated nurture instead of SDR outreach) protects sales capacity for the leads most likely to convert. Combine with company enrichment and domain age to triage your full inbound pipeline.

See what the API returns

Every MX record lookup returns a structured JSON response. Here is what a request returns for a domain:

Response parameters

email_address

String
The email address you submitted for analysis.

email_deliverability.status

String
Whether the email is considered deliverable, undeliverable, or unknown.

email_deliverability.status_detail

String
Additional detail on deliverability (e.g., inbox_full, full_mailbox, invalid_format).

email_deliverability.is_format_valid

Boolean
Is true if the email follows the correct format.

email_deliverability.is_smtp_valid

Boolean
Is true if the SMTP check was successful.

email_deliverability.is_mx_valid

Boolean
Is true if the domain has valid MX records.

email_deliverability.mx_records

Array
List of MX records associated with the domain.

email_quality.score

Float
Confidence score between 0.01 and 0.99 representing email quality.

email_quality.is_free_email

Boolean
Is true if the email is from a known free provider like Gmail or Yahoo.

email_quality.is_username_suspicious

Boolean
Is true if the username appears auto-generated or suspicious.

email_quality.is_disposable

Boolean
Is true if the email is from a disposable email provider.

email_quality.is_catchall

Boolean
Is true if the domain is configured to accept all emails.

email_quality.is_subaddress

Boolean
Is true if the email uses subaddressing (e.g., user+label@domain.com).

email_quality.is_role

Boolean
Is true if the email is a role-based address (e.g., info@domain.com, support@domain.com).

email_quality.is_dmarc_enforced

Boolean
Is true if a strict DMARC policy is enforced on the domain.

email_quality.is_spf_strict

Boolean
Is true if the domain enforces a strict SPF policy.

email_quality.minimum_age

Integer
Estimated age of the email address in days, or null if unknown.

email_sender.first_name

String
First name associated with the email address, if available.

email_sender.last_name

String
Last name associated with the email address, if available.

email_sender.email_provider_name

String
Name of the email provider (e.g., Google, Microsoft).

email_sender.organization_name

String
Organization linked to the email or domain, if available.

email_sender.organization_type

String
Type of organization (e.g., company).

email_domain.domain

String
Domain part of the submitted email address.

email_domain.domain_age

Integer
Age of the domain in days.

email_domain.is_live_site

Boolean
Is true if the domain has a live website.

email_domain.registrar

String
Name of the domain registrar.

email_domain.date_registered

Datetime
Date when the domain was registered.

email_domain.date_last_renewed

Datetime
Last renewal date of the domain.

email_domain.date_expires

Datetime
Expiration date of the domain registration.

email_domain.is_risky_tld

Boolean
Is true if the domain uses a top-level domain associated with risk.

email_risk.address_risk_status

String
Risk status of the email address: low, medium, or high.

email_risk.domain_risk_status

String
Risk status of the domain: low, medium, or high.

email_breaches.total_breaches

Integer
Total number of data breaches involving this email.

email_breaches.date_first_breached

Datetime
Date of the first known breach.

email_breaches.date_last_breached

Datetime
Date of the most recent breach.

email_breaches.breached_domains

Array
List of breached domains.

email_breaches.breached_domains[].domain

String
Domain affected by the breach.

email_breaches.breached_domains[].date_breached

Datetime
Date when the breach occurred.

API Endpoint

curl --request GET \
  --url https://emailreputation.abstractapi.com/v1
{
  "email_address": "benjamin.richard@abstractapi.com",
  "email_deliverability": {
    "status": "deliverable",
    "status_detail": "valid_email",
    "is_format_valid": true,
    "is_smtp_valid": true,
    "is_mx_valid": true,
    "mx_records": [
      "gmail-smtp-in.l.google.com",
      "alt3.gmail-smtp-in.l.google.com",
      "alt4.gmail-smtp-in.l.google.com",
      "alt1.gmail-smtp-in.l.google.com",
      "alt2.gmail-smtp-in.l.google.com"
    ]
  },
  "email_quality": {
    "score": 0.8,
    "is_free_email": false,
    "is_username_suspicious": false,
    "is_disposable": false,
    "is_catchall": true,
    "is_subaddress": false,
    "is_role": false,
    "is_dmarc_enforced": true,
    "is_spf_strict": true,
    "minimum_age": 1418
  },
  "email_sender": {
    "first_name": "Benjamin",
    "last_name": "Richard",
    "email_provider_name": "Google",
    "organization_name": "Abstract API",
    "organization_type": "company"
  },
  "email_domain": {
    "domain": "abstractapi.com",
    "domain_age": 1418,
    "is_live_site": true,
    "registrar": "NAMECHEAP INC",
    "registrar_url": "http://www.namecheap.com",
    "date_registered": "2020-05-13",
    "date_last_renewed": "2024-04-13",
    "date_expires": "2025-05-13",
    "is_risky_tld": false
  },
  "email_risk": {
    "address_risk_status": "low",
    "domain_risk_status": "low"
  },
  "email_breaches": {
    "total_breaches": 2,
    "date_first_breached": "2018-07-23T14:30:00Z",
    "date_last_breached": "2019-05-24T14:30:00Z",
    "breached_domains": [
      { "domain": "apollo.io", "date_breached": "2018-07-23T14:30:00Z" },
      { "domain": "canva.com", "date_breached": "2019-05-24T14:30:00Z" }
    ]
  }
}

API Response

Disposable email checker FAQ

What is a disposable email address?

A disposable email address is a temporary mailbox provided by services like Mailinator, Guerrilla Mail, 10MinuteMail, or Temp-Mail. The user gets an inbox they can read for minutes or hours, then discards. Disposable emails are commonly used to bypass signup gates, claim free trials repeatedly, and avoid marketing follow-up. The address looks like a normal email but routes to a provider known for hosting throwaway inboxes.

How does disposable email detection work?

Detection works by matching the domain portion of an email against a curated list of known disposable providers. Abstract maintains a list of 8M+ disposable domains updated daily as new throwaway services launch. When you submit an address, the tool extracts the domain (everything after the @), looks it up in the list, and returns true if there's a match. Detection is domain-based, not address-based, so the result is the same for every address at a given disposable provider.

Why are disposable emails a problem?

Disposable signups inflate user counts without producing real users. They skew engagement metrics, waste sales outreach effort, and hide free-trial abuse. For B2B products, a high disposable rate often correlates with weak product-led growth signals because the people most willing to sign up with a throwaway address are the least likely to convert. For email senders, sending to disposable addresses hurts sender reputation since the inboxes are abandoned within hours.

Should I block all disposable emails?

Not necessarily. A small share of legitimate users use disposable addresses for privacy, and blocking them outright loses real signups. The better approach is to flag disposable signups, route them through a stricter verification path (email confirmation, payment-only access, or manual review), and reserve outright blocks for high-risk flows like free trials and refundable purchases. Treat the disposable signal as one input to a risk score, not a binary gate.

Can I tell if an email is disposable from the domain alone?

Yes. Disposable detection is entirely domain-based. The username (the part before the @) does not matter. If the domain matches a known disposable provider, every address at that domain is treated as disposable. This is also why some legitimate users get caught: a privacy-conscious user creating an account at a disposable provider is indistinguishable from an abuser doing the same thing.

How accurate is disposable email detection?

Detection accuracy is a function of the underlying domain list. New disposable services launch every week, so a stale list misses recent providers. Abstract's list is updated daily and currently covers 8M+ domains. False positives are rare and usually involve niche email providers that look disposable but aren't. False negatives happen when a brand-new disposable service hasn't been catalogued yet, but the catalog is refreshed quickly enough that most operators are caught within days of launch.

Need to check thousands of addresses?
stars rating
4.8 from 1,863 votes
The same lookup the tool runs, available as an API. No credit card required.
get free api key
No credit card required