How to tell if an email address is fake
· 6 min read · Disposable email
You can tell an email address is fake by running five checks: is the domain a known disposable provider, does the part before the @ look machine-generated, is the domain a typo of a real provider (gmial.com), does the domain exist and accept mail, and is it a role account like info@ rather than a person. A sixth check, asking the mail server whether the mailbox exists, catches well-formed addresses that go nowhere. None of these proves the address belongs to the person who typed it. Only a confirmation email they click does that.
"Fake" covers several different things, and they need different responses:
| Kind of fake | Example | Receives mail? | Typical intent |
|---|---|---|---|
| Disposable | x8@mailinator.com |
Briefly | Skip your confirmation, grab a trial |
| Random or bot-made | qz7kx2mp@gmail.com |
Maybe | Automated account creation |
| Typo | jane@gmial.com |
No | Honest mistake |
| Made-up domain | test@asdfgh.com |
No | Get past a required field |
| Doesn't exist at a real domain | nobody123@outlook.com |
No | Get past a required field |
| Role account | info@acme.com |
Yes, a shared inbox | Often legitimate; poor for outreach |
Check 1: is the domain disposable?
Disposable email services hand out inboxes that work for minutes or hours, without signup. People use them to receive a confirmation link and never return. You recognise them by domain, and there are thousands of domains. The community disposable-email-domains list on GitHub holds roughly ten thousand of them.
Manually: search the domain name. Disposable services advertise themselves; the homepage usually shows a temporary inbox. Our disposable category page shows what the category looks like.
In code: match the registrable domain against a maintained list, not a hand-written array. Lists go stale as new domains appear weekly, which we explain in why disposable email blocklists go stale. Check the registrable domain (mail.example.com becomes example.com) so subdomains don't slip through.
Check 2: does the local part look machine-generated?
Bots that create accounts at scale often use random strings: xk7qmz2p@gmail.com, bnvhgtyu8823@outlook.com. Humans tend to use names, words and birth years.
Manually: try to read it aloud. Long runs of consonants, mixed letters and digits with no pattern, and strings that aren't a name or word are suspicious.
In code: score how "word-like" the string is. A character-bigram model does this well: it measures how often each pair of letters appears in real names and words. Detecting machine-generated email addresses has a runnable scorer.
Be careful here. Short names, initials (jkl@), and names from languages your model wasn't trained on can score as random. So do privacy relay aliases, which are random by design and forward to real people; see Apple Hide My Email, Firefox Relay and SimpleLogin are not disposable. Use randomness as a reason to look closer or add friction, not as a block on its own.
Check 3: is it a typo of a real provider?
gmial.com, hotmial.com, yaho.com and gmail.co are mistakes, not fraud. Some of those typo domains are registered by third parties, so the address may even pass a DNS check while your mail goes to a stranger.
Manually: compare the domain to the big providers your users actually use. One swapped or missing letter is the giveaway.
In code: compute an edit distance against a short list of popular domains like gmail.com, outlook.com and yahoo.com, and suggest the correction instead of rejecting. Catching email typos at signup has the UI side: suggest, don't silently change.
Check 4: does the domain exist and accept mail?
test@asdfgh.com and me@nope.invalid are typed to get past a required field. Check DNS:
- No DNS answer at all (
NXDOMAIN): the domain isn't registered. Fake. - A domain with no MX record and no A record: nothing can receive mail there.
- A null MX (
MX 0 ., defined in RFC 7505): the domain explicitly accepts no mail.
Manually:
dig +short MX asdfgh.com
dig +short A asdfgh.com
Empty output on both is a strong signal. A DNS timeout is not; retry before you decide.
Check 5: is it a person or a role account?
info@, admin@, sales@, support@ and noreply@ are real addresses, but they belong to a function, not a person. For a B2B signup, info@acme.com might be a legitimate small company. For a contest entry or a free trial, it's a way to look official without identifying anyone. noreply@ and mailer-daemon@ should never be typed into a form by a human.
We don't recommend blocking role accounts outright. Flag them and decide per flow. Role-based email addresses goes through the cases.
Check 6: does the mailbox exist?
nobody123@outlook.com passes every check above: the domain is real, the local part looks fine, it isn't a typo. The only way to catch it without sending is to ask Outlook's mail server, using an SMTP RCPT TO probe that stops before any message is sent. How to verify an email address without sending an email explains how it works and why it can't answer for catch-all domains.
Doing all six with two API calls
For signups, where you need a fast answer, a lookup call with skip_enrichment: true returns the category and the address signals in milliseconds, without the company profile:
// is-fake.mjs (Node 18+)
const KEY = process.env.PINGUTIL_KEY;
export async function emailRisk(email) {
const res = await fetch('https://pingutil.com/v1/lookup', {
method: 'POST',
headers: { authorization: `Bearer ${KEY}`, 'content-type': 'application/json' },
body: JSON.stringify({ input: email, skip_enrichment: true, check_dns: true }),
signal: AbortSignal.timeout(5_000),
});
if (!res.ok) return null; // fail open: don't block signups on an outage
const d = await res.json();
return {
category: d.category, // 'disposable', 'free', 'company', ...
block: d.verdict.is_spam, // disposable or randomized
review: d.verdict.low_trust, // role, system or sales address
reason: d.verdict.reason,
randomness: d.email_signals?.randomness_score ?? null, // 0-100
domainExists: d.domain_signals?.domain_exists ?? null,
canReceiveEmail: d.domain_signals?.can_receive_email ?? null,
};
}
console.log(await emailRisk(process.argv[2]));
node is-fake.mjs qz7kx2mp@mailinator.com
verdict.is_spam is true for disposable domains, reputation-flagged domains and randomized local parts; verdict.low_trust flags role, system and sales addresses without blocking. Block on the first, review or route on the second. One limitation to know: can_receive_email treats a null MX domain as mail-capable, so use the verify call below if that edge case matters to you.
For the mailbox check and typo suggestions, call POST https://pingutil.com/v1/verify with {"email": "..."}. It returns status (valid, invalid, risky, unknown), a reason such as mailbox_not_found, no_domain, null_mx or disposable_domain, and did_you_mean when the domain looks like a typo of a major provider. Show did_you_mean back to the user rather than rejecting them. Try both in the live demo, and see request and response fields in the API reference.
What to do once you know
| Signal | Signup / trial | Lead form | List cleaning |
|---|---|---|---|
| Disposable domain | Block or require a work email | Drop | Remove |
| Randomized local part | Add friction (CAPTCHA, phone, confirm first) | Review | Remove if it never engaged |
| Typo domain | Suggest the correction | Suggest the correction | Fix if obvious, else remove |
| Domain missing or no MX | Reject with a clear message | Drop | Remove |
| Mailbox doesn't exist | Reject with a clear message | Drop | Remove |
| Role account | Allow, flag | Route to review | Keep for newsletters, skip for outreach |
| Catch-all or unknown | Allow, confirm by email | Allow | Send carefully |
Whatever you check up front, keep the confirmation email. It is the only test a fake address can't pass, and it costs real users one click.
Questions people ask
- Can an email address look real but be fake?
- Yes. An address can be well formed, use a real domain and still go nowhere, like jane.doe@gmail.com typed by someone who isn't Jane. Only a mailbox check, and ultimately a confirmation email the person clicks, proves the address is real and theirs.
- Is a disposable email address fake?
- It is real in the sense that it receives mail, usually for a short time. It is fake in the sense that the person won't read it next week. Most products treat disposable addresses as untrustworthy for accounts, trials and leads.
- Are Apple Hide My Email addresses fake?
- No. Relay services like Apple Hide My Email, Firefox Relay and SimpleLogin forward to a real, long-lived inbox. Their local parts look random, so some random-address checks flag them, but blocking them shuts out real privacy-minded users.