What counts as a disposable email address?

An inbox from a service whose purpose is to be thrown away: no account, public or short-lived, made to get past a signup and never read again. Mailinator and 61,732 other domains on the current list.

How current is the list?

It is generated from two open, maintained lists; the version you were checked against is in meta.ruleset.

Will it catch a brand-new throwaway service?

Not until the source lists add it. The check is a list lookup, and a list has edges.

Do you keep the addresses?

No. The request is processed in memory and dropped; nothing is written to a database, storage or logs.

FREE TOOL

Disposable email checker

Enter an address and see whether its domain is one of 61,733 known disposable or temporary email providers (list generated 2026-09-27). The check is a lookup against that list: a throwaway service created since the list was built is not on it, and an address on a normal domain used once and abandoned is not disposable by this definition. The address itself is not contacted.

INPUT

try

200 OK13 ms (api)

BLOCK

Domain "mailinator.com" is a known disposable/throwaway email provider

6 checks run

Yes — a known disposable domain

code: email.disposable_domain
severity: high

{
  "ok": true,
  "verdict": "block",
  "findings": [
    {
      "code": "email.disposable_domain",
      "severity": "high",
      "message": "Domain \"mailinator.com\" is a known disposable/throwaway email provider",
      "source": "rules"
    }
  ],
  "data": {
    "mx": [
      {
        "host": "mail.mailinator.com",
        "preference": 1
      },
      {
        "host": "mail2.mailinator.com",
        "preference": 1
      }
    ]
  },
  "checks_run": [
    "email.alias_normalisation",
    "email.disposable",
    "email.mx",
    "email.role_account",
    "email.syntax",
    "email.typo_domain"
  ],
  "checks_skipped": [
    {
      "code": "ip.not_public",
      "reason": "plan",
      "available_on": "starter"
    },
    {
      "code": "ip.hosting_provider",
      "reason": "plan",
      "available_on": "starter"
    },
    {
      "code": "ip.tor_exit",
      "reason": "plan",
      "available_on": "starter"
    }
  ],
  "meta": {
    "gate": "emails",
    "ms": 13,
    "ruleset": "reference-a39927da"
  }
}

The full /v1/emails gate also checks

Address normalisationdisposable_infrastructureMX recordsprovider_typeRole accountAddress syntaxTypo domainyoung_domainasnCloud hosting IPPrivate IP rangeTor exit nodevpn_provider

Also available through the API.

Join the waitlist /v1/emails docs

Live call to the same /v1 endpoint customers use. Rules only on this page; nothing you type is stored.

What it checks

email.disposable — the address's domain against the embedded list, built from disposable-email-domains/disposable-email-domains (CC0) and FGRibreau/mailchecker (MIT), versioned through StormDoor's reference-data pipeline rather than fetched per request. The list's date is printed with the result as meta.ruleset.

The rest of /v1/emails runs on the same call: syntax, MX, role account, typo domain, alias normalisation. See the email checker.

Why it matters

A disposable inbox gets a user through a signup and out the other side with no way to reach them and no reason to come back. Blocking the domain at the form costs nothing and catches the lazy case; the deliberate case (a new service, a normal domain with catch-all) is not on any list, which is why this check is high and not critical, and why the email checker runs five other checks alongside it.

Disposable email checker

What it checks

What the result means

Why it matters

Disposable addresses,
answered.

From your own code

Read more

Guides about this

Disposable email checker

What it checks

What the result means

Why it matters

Disposable addresses,answered.

From your own code

Read more

Guides about this

Disposable addresses,
answered.