Auth0 on its own
- A Gmail, Outlook or iCloud address looks just like a work email
- Throwaway inboxes restart free trials again and again
- You keep your own list of free email domains, and it goes stale
- Typos like [email protected] become lost leads and bounces
Auth0 + isBusinessEmail()
- Every address gets a category: business, personal, disposable, relay, education
- Disposable and relay inboxes are caught, including new services on known mail servers
- Lists and DNS checks are maintained for you, behind one HTTP call
- did_you_mean suggests a fix for typos, and you see whether the company runs Google Workspace or Microsoft 365
Try it from your terminal
Before you set up Auth0, see what the API returns. Test addresses need no key; for real addresses use a free key. Full reference.
# Test addresses need no key
curl -sG https://api.isbusinessemail.com/v1/check \
--data-urlencode "[email protected]"curl -s https://api.isbusinessemail.com/v1/check \
-H "Authorization: Bearer $IBE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"[email protected]","policy":"b2b"}'{
"email": "[email protected]",
"is_business": false,
"category": "personal",
"recommendation": "block",
"policy": "b2b",
"is_free_provider": true,
"is_disposable": false,
"did_you_mean": null,
"workspace": {
"google_workspace": { "detected": false },
"microsoft_365": { "detected": false }
}
}Auth0 Actions run your code during authentication flows. The Pre User Registration trigger runs before a user is created in a database or passwordless connection, which is exactly where a work-email check belongs.
1. Store the key as a secret
In the Action editor, add a secret named IBE_API_KEY with your ibe_live_… key. Never hard-code it.
2. The Action
Create an Action on the Pre User Registration trigger:
exports.onExecutePreUserRegistration = async (event, api) => {
const email = event.user.email;
if (!email) return;
let verdict;
try {
const res = await fetch('https://api.isbusinessemail.com/v1/check', {
method: 'POST',
headers: {
Authorization: `Bearer ${event.secrets.IBE_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({ email, policy: 'b2b' }),
signal: AbortSignal.timeout(2500),
});
if (!res.ok) return; // fail open: never block signups on our errors
verdict = await res.json();
} catch {
return; // timeout or network error: fail open
}
if (verdict.recommendation === 'block') {
const hint = verdict.did_you_mean ? ` Did you mean ${verdict.did_you_mean}?` : '';
api.access.deny('work_email_required', `Please sign up with your work email.${hint}`);
return;
}
api.user.setUserMetadata('email_category', verdict.category);
api.user.setUserMetadata('google_workspace', verdict.workspace?.google_workspace?.detected ?? false);
api.user.setUserMetadata('microsoft_365', verdict.workspace?.microsoft_365?.detected ?? false);
};
Deploy it and add it to the Pre User Registration flow.
- The second argument to
api.access.denyis the message the user sees; keep it friendly. - Metadata lets your app read the verdict later (for example to pre-select a Microsoft or Google connector).
3. Social connections
Pre User Registration doesn’t run for social connections such as “Sign in with Google”. For those, classify on the first login with a Post Login Action (for example when it’s the user’s first login) and either deny access or flag the account. Remember that a Google social login can be a personal @gmail.com account.
Tips
- Use
policy: 'strict'if your product needs a company tenant from day one;unknownand role accounts are then blocked too. - Actions have execution time limits. Keep the timeout around 2–3 s and fail open.
- Test with
[email protected](denied) and[email protected](allowed).
Official docs: Auth0 documentation (see Actions and the Pre User Registration trigger). See also: Categories and policies.