Disposable Email Checker
Enter an email address or a domain to see if it belongs to a throwaway email service. The check runs in your browser against a public list of 9,222 disposable domains, then looks up where the domain's mail goes.
Only the domain is checked. The part before the @ stays in your browser.
List: disposable-email-domains (CC0 1.0), 9,222 domains, last changed 9 October 2026.
What the checker looks at
- The list. The domain, and every parent domain above it, is matched against the disposable-email-domains list. The list stores registrable domains, so an address at mail.sub.example.com is matched against example.com too.
- The mail servers. Your browser asks a public DNS-over-HTTPS service for the domain's MX records, which name the servers that accept its mail. A domain with no MX records, or a null MX record, can't really receive mail.
- Who runs those servers. If the MX servers belong to a domain on the list, the address is almost certainly disposable even when its own domain is new. Throwaway services often add fresh domains that all point at the same mail servers.
Where the list comes from
The domains come from the open-source disposable_email_blocklist.conf file on GitHub, maintained by volunteers since 2014 and released under CC0, so anyone may copy and use it. Its README quotes PyPI, the Python package index, saying it uses the list to block throwaway domains at sign-up. Anyone proposing a new domain is asked for a screenshot of a site handing out addresses on it.
Our copy has 9,222 domains. The list was last changed on 9 October 2026, and our copy was taken on 9 October 2026. A script refreshes it every time the site is built.
What it can't tell you
- Whether one particular mailbox exists. That needs a conversation with the mail server, which this page does not attempt.
- Whether a domain is brand new and not yet reported. Lists always lag. The MX check narrows the gap but does not close it.
- Whether a person is real. Plenty of people use temp mail for privacy, and plenty of fake accounts use Gmail.
Using the list in your own sign-up form
Download the file from GitHub, load it into a set, and check the address's domain and each parent domain. In JavaScript:
const parts = email.split("@").pop().toLowerCase().split(".");
const isDisposable = parts
.slice(0, -1)
.some((_, i) => blocklist.has(parts.slice(i).join(".")));Refresh your copy every week or so, since the list changes most days. Show a plain message when you refuse an address, such as "Please use an email address you'll keep", so real people know what to do. And leave alias services alone: an address at duck.com or mozmail.com forwards to a real person who simply doesn't want to hand over their main inbox.
A note on our own addresses
This site gives out temporary addresses, and the domains they used were on this list when we checked in October 2026. Sites that check it will refuse them, which is their right. If that happens to you, the email alias guide covers what to use instead. For when to use temp mail at all, start at the temp mail inbox.
Questions
Does this check whether the mailbox itself exists?
No. It checks the domain only: whether it is on the list and whether it has mail servers. Testing a single mailbox means talking to the mail server directly, which many servers refuse or answer falsely, and which this page does not do.
Is my address sent anywhere?
Only the part after the @. Your browser downloads the list from this site and checks it locally, then asks Cloudflare's public DNS (or Google's if Cloudflare doesn't answer) for the domain's mail servers. The part before the @ never leaves your browser, and this site does not log what you check.
A domain I know is disposable says not listed. Why?
New throwaway domains appear all the time, and a list only knows the ones someone has reported. The mail server check catches some of these, when the domain's mail goes to a provider that is on the list.
Should my sign-up form block every listed domain?
That is your call. Blocking cuts throwaway sign-ups, but some real people use temp mail because they don't trust a site yet. A softer option is to accept the address and limit what an unverified account can do. Either way, don't block alias services such as Firefox Relay or DuckDuckGo: they forward to a real inbox.
Are this site's own addresses on the list?
Yes. The domains our inbox hands out were on it when we checked in October 2026, so sites that use this list will refuse those addresses. We would rather say so than pretend otherwise.