Disposable email detection that keeps temp mail out of your product.
Trueguard blocks disposable, temporary and alias email addresses at signup using a registry that is updated continuously as new temp-mail domains appear. Aliases are normalised to the inbox behind them, so one person cannot turn a single mailbox into twenty accounts.
No credit card required - free tier availableSignup verification
Disposable email>70M Verifications
Signup events scored across customer products to date.
25% Of users
On some products, up to a quarter of signups arrive from disposable or aliased inboxes.
>90% Detection
Temporary and alias addresses flagged before the account is created.
Signs temporary emails are reaching your signup form.
Temp-mail signups look ordinary one at a time. The pattern shows up in your deliverability numbers and in a contact list you can no longer email. If two or more of these look familiar, you need to block disposable emails at signup.
See how detection worksBounce rates keep climbing
Temporary inboxes expire within minutes, so onboarding and receipt emails have nowhere to land.
Your contact list is full of dead addresses
Marketing spend goes to records that were never reachable, and sender reputation suffers with it.
Signups cluster on a handful of domains
The same disposable providers and plus-address aliases show up again and again in your CRM.
Your blocklist never stays current
Someone maintains a list of temp-mail domains by hand while new ones launch every week.
How it works
Disposable email detection, from address to action.
New temp-mail services appear constantly and most of them look like ordinary domains with valid MX records. Temporary email detection checks the domain, the mailbox pattern and the device behind the request, then hands your backend a score and a decision before the account exists.
Step 1
A registry that stays current
Thousands of disposable and temporary-mail domains, updated continuously as services launch, rebrand and rotate. Domain age, MX configuration and catch-all behaviour are checked alongside the list itself.
Read the email validation docsStep 2
Alias and subaddress normalisation
Plus-addresses, dot variants, private relays and forwarding services are resolved back to the mailbox behind them, so twenty spellings of one inbox count as one account.
Try the free email checkerStep 3
Your rules, your action
Design rules your way - block the address, require a work email, hold the account for review, or let it through and flag it. Every decision returns in the API response, so nothing needs a dashboard visit.
Read the Event API referenceOne check, four problems it solves.
Disposable email detection
Every address is checked against a live registry of disposable domains before the account is created, so temp-mail signups never enter your database in the first place.
Temporary email detection
Ten-minute inboxes, burner email signups and throwaway forwarders are identified by domain age, MX setup and catch-all behaviour, not just by a static list someone has to maintain.
Disposable email detection API
The disposable email checker returns whether an address is disposable, role-based, an alias or undeliverable in one REST call, plus the reason. Use the disposable email API at signup, on import, or to clean a list you already have.
Email alias detection and plus-addresses
Plus-address detection resolves name+1@, name+2@ and dotted variants to the one mailbox behind them. Trueguard reports the canonical inbox so per-account limits mean what you intended.
Same person coming back for another trial? See free trial abuse prevention, or fake account detection for bots and scripted registrations.
What basic checks miss.
A regex blocklist, an MX lookup and a CAPTCHA each answer one narrow question. None of them tell you whether the inbox will still exist tomorrow or whether it belongs to someone you already have.
| Signup pattern | Trueguard | Static blocklist | MX / SMTP check | CAPTCHA |
|---|---|---|---|---|
| Known disposable domain | ||||
| Temp-mail domain registered this week | ||||
| Catch-all inbox with valid MX records | Partial | |||
| Plus-address and dotted aliases of one inbox | ||||
| Private relay and forwarding addresses | ||||
| One person across many temporary addresses |
Check if your product is targeted by temporary emails.
Enter your domain to see how many of your emails landed in public disposable inboxes we monitor around the clock.
Example report
Live in an afternoon.
Call the Email Validation API directly for a single address, or install the JavaScript snippet and use the Event API to score the whole signup. Either way the verdict, the reason and the rule action come back in the response.
POST /v2/event
{
"eventId": "0198b326-025b-7c30-8605-b99796c5e953",
"action": "block",
"scores": { "risk": 0.94, "bot": 0.2 },
"signals": {
"disposable_email": {}
},
"email": {
"email": "ro.n.de.ysko.ch@googlemail.com",
"rawEmail": "rondeyskoch@gmail.com",
"disposable": true,
"domain": { "name": "googlemail.com" }
},
"fingerprint": {
"identifier": "7f56c04d-4652-471b-b5dd-426ad3bd9504",
"incognito": false
}
}One endpoint, one answer
No SDK sprawl and no changes to your auth flow. Validate the address where you create the account.
Decide in your own code
Trueguard returns the verdict and the reason. Whether that blocks the signup, asks for a work email or just flags it stays your call.
No friction for real users
The check is a single call at submit time. Genuine signups see nothing - no CAPTCHA, no confirmation loop, no added latency they can notice.
The cost of leaving it alone.
10-60 hrs
per week
Maintaining a temp-mail blocklist by hand
1-3 FTEs
ongoing
Engineering time on in-house email checks
$5K-$75K
per month
Wasted email, storage and onboarding spend
$25K-$200K
per year
Marketing budget spent on unreachable contacts
Frequently asked questions.
Disposable email detection, aliases and what the check does to your signup flow.
Keep reading
Free trial abuse prevention
Detect the same person returning for another trial under a new email address.
Fake account detection
Stop bot registrations and scripted signups before they reach your database.
Email validation API
Validate deliverability, role-based addresses and disposable domains in one REST call.
