# Disban > Disban is an email-domain classification API (Free beta). It classifies a domain as disposable, free, alias, testing, parked or unknown so you can protect signups. ## Discover - API base: https://disban.io - [OpenAPI 3.1](https://disban.io/openapi.json) - [Plan catalog](https://disban.io/api/plans) - [Human quickstart](https://disban.io/agents) - [API documentation](https://disban.io/docs) ## Try it without a key GET https://disban.io/api/v1/check/{email or domain} returns {"domain","category","disposable","mail_routing"}. No signup or key. Call it from your server, not the browser (browser cross-origin requests get 403). Limits: 10 per hour and 30 per day per network, then HTTP 429 with Retry-After. disposable is null when the category is unknown: treat that as unverified, not safe. For production signup traffic, use a free API key (2,000 checks per month, full evidence, batch) with POST /api/check below. Example: curl https://disban.io/api/v1/check/sharklasers.com -> {"domain":"sharklasers.com","category":"disposable","disposable":true,"mail_routing":"routable"} ## SDK, CLI and MCP (npm and PyPI: disban) Start without signing up: npm install disban (or pip install disban) works immediately on the keyless allowance. When it runs out, get a free key from the terminal with npx disban signup (or disban signup): name, email, the emailed 6-digit code, and the key is printed and can be saved to ./.env as DISBAN_API_KEY. npx disban login issues a key for an existing account. npm install disban. import { signupDecision } from "disban"; const d = await signupDecision(email); then block when d.action is "block", ask for a correction when "fix", otherwise create the account and hold free credits when d.hold is true. It fails open (allow with hold) if Disban is slow, unreachable or rate-limited. Without DISBAN_API_KEY it uses the keyless endpoint; with it, POST /api/check. CLI: npx disban check someone@example.com Hosted MCP server (Streamable HTTP, uses your API key and plan credits; tools check_email_domain, check_email_domains, get_usage): claude mcp add --transport http disban https://disban.io/mcp --header "Authorization: Bearer $DISBAN_API_KEY" Local MCP server (keyless or DISBAN_API_KEY): claude mcp add disban -- npx -y disban mcp ## Plans - free: 2000 checks per UTC calendar month; 1 HTTP check/batch requests per second; $0. Available for activation. - launch: 10000 checks per UTC calendar month; 5 HTTP check/batch requests per second; not available. Coming soon; not selectable. - growth: 100000 checks per UTC calendar month; 15 HTTP check/batch requests per second; not available. Coming soon; not selectable. - scale: 1000000 checks per UTC calendar month; 30 HTTP check/batch requests per second; not available. Coming soon; not selectable. Free is the only plan available for activation: 2,000 checks per UTC month and one active API key. Launch, Growth, and Scale are coming soon. No payment or automatic billing. Successful domain checks consume credits; failed checks are refunded. Plan changes preserve usage. Activity retention follows your current plan: Free 15 days, Launch 30, Growth 60, Scale 90. Expired activity is deleted; upgrades do not restore deleted records. Saved results are never recalculated. ## Activate with owner authorization 1. GET /api/plans to inspect current plans and launch terms. 2. POST /api/auth/otp/request with JSON {"intent":"signup","name":"OWNER_NAME","email":"OWNER_EMAIL","plan_id":"free"}. Disban checks the signup domain before sending a code. With the owner's authorization, submit the emailed code to POST /api/auth/otp/verify {"intent":"signup","challenge_id":"RETURNED_ID","code":"SIX_DIGIT_CODE"}. Save the returned session cookie securely. Existing accounts use intent "login" for both requests. Password authentication is disabled. Codes expire in ten minutes, permit five attempts and can be used once. Never store codes in logs or source control. 3. POST /api/keys with the session cookie and JSON {"name":"Agent integration"}. The response contains token, shown only once. Store it in a secret manager, not in logs or source control. 4. POST /api/check with Authorization: Bearer TOKEN and JSON {"input":"sharklasers.com"}. Or POST /api/batch with {"inputs":["gmail.com","yopmail.com"]}, maximum 50 entries. 5. GET /api/subscription with Bearer TOKEN to inspect the selected plan, usage and reset time. remaining includes unexpired referral credits; monthly_remaining and bonus_remaining separate the balances. Monthly credits are used first, then bonus credits by expiry. Failed checks refund their original source. GET /api/referrals requires an owner session and returns the referral link and reward policy. Change plan with POST /api/subscription {"plan_id":"free"} using the owner's session, not an API key. Switching plans does not reset usage. 6. DELETE /api/keys/{id} using the session cookie to revoke a key. POST /api/auth/logout with {} to end the session. All POSTs require Content-Type: application/json. Browser cross-origin calls are rejected; use server-side HTTP. Signup returns 201 and Set-Cookie. A key is scoped to check, batch, inbound check webhook and read-only subscription usage; it cannot administer accounts or keys. No payment method is collected and no money is charged. ## Lookup, realtime and incoming webhook Add ?realtime=false to /api/check or /api/batch for stored fresh evidence only. Add ?realtime=true to wait for bounded live routing. Missing or stale lookup evidence is unknown, never a safe result. Omitted mode preserves standard verification. POST /api/webhooks/check accepts {"input":"person@example.com"} or {"inputs":["example.com","example.org"]} and returns ordered results immediately. It defaults to lookup-only; ?realtime=true enables live checks. Use the same API key and quotas. This is an inbound push endpoint, with no outbound callback. Unknown domains join discovery using domain names only. A queued candidate does not become a disposable seed automatically. ## Results and errors Activity retention follows the current plan: Free 15 days, Launch 30 days, Growth 60 days, Scale 90 days. A plan change applies the new retention window to existing activity. Expired records are deleted and cannot be restored by upgrading. Saved results are never recalculated; new checks create new results. Monthly credit usage is independent of activity retention. Unavailable enrichment fields are null, not negative results. email and normalized_email are request-only echoes and are never retained in history. disposable is null when unresolved. SPF, DMARC, authority, spam reputation, MX provider metadata, role detection, and typo suggestions are not yet collected. MX priorities are null until collected. Use category (disposable, free, alias, testing, parked, unknown), reason, and optional matched_on. Unknown is not verified safe. Alias is distinct from disposable. This is domain classification, not mailbox existence verification. Inspect mail_routing separately: invalid means no current public mail route; unknown means verification is pending or temporarily unavailable; routable does not prove a mailbox exists. Cold and expired routing checks wait up to 2.5 seconds for verification. Unresolved routing returns HTTP 503 with code verification_unavailable and Retry-After matching the cached DNS retry deadline (five seconds when no deadline is available), rather than a successful pending verdict. Batch failures carry status 503 per entry. No credit is charged and no successful check is saved. Retry with backoff and respect rate limits. A returning domain may have reason reassessment_required; historical evidence alone does not restore a disposable verdict. 400 invalid input; 401 missing/expired credentials; 403 cross-origin; 409 duplicate account or key limit; 413 oversized body; 415 wrong content type; 429 rate or quota exceeded (Retry-After header); 502 checker unavailable; 503 verification unavailable (Retry-After header). Batch errors appear per entry; failed entries are refunded. Cache hits cost one credit. A batch uses one request-rate slot and one monthly credit per successful entry. Do not blindly retry successful checks: checking has no idempotency key and repeated successes consume credits. Only Free is available for activation, with one active API key. Future paid plans require explicit opt-in. No SLA, team seats, outbound webhook callbacks, or mailbox delivery guarantee is offered in this preview. --- ## Guides - [The best disposable email detection APIs in 2026, compared](https://disban.io/blog/best-disposable-email-detection-apis): Disban, UserCheck, Kickbox, ZeroBounce, Abstract API, DeBounce and open-source lists: free tiers, entry prices, what each checks, and which fits signup protection. - [How to block disposable emails before sending with Resend (Node.js)](https://disban.io/blog/block-disposable-emails-before-sending-with-resend): Resend does not check whether an address is disposable. Check the domain with Disban first, then send the verification email with Resend only when the address is allowed. - [What is a disposable email address?](https://disban.io/blog/what-is-a-disposable-email-address): A disposable email address is a temporary inbox that works for minutes or days and is then abandoned. How they work, how they differ from free email and aliases, and how to recognise one. - [How to detect disposable email addresses: five methods compared](https://disban.io/blog/how-to-detect-disposable-email-addresses): Blocklists, mail-server checks, operator matching, APIs and behaviour signals: what each method catches, what it misses, and which combination works at signup. - [Is Gmail a disposable email? Free email vs disposable email](https://disban.io/blog/is-gmail-a-disposable-email): No. Gmail, Outlook and Proton Mail are free email providers with long-term inboxes. Why some blocklists include them anyway, and how to treat free email at signup. - [How temporary email services work, and why new domains keep appearing](https://disban.io/blog/how-temporary-email-services-work): Temporary email services run many domains on the same mail servers and replace them as they get blocked. Our October 2026 data on Yopmail, Mailinator and generator.email shows the pattern. - [Should you block disposable email addresses?](https://disban.io/blog/should-you-block-disposable-emails): Usually yes for free trials and credits, but not always outright. When to block, when to allow with limits, and how to avoid turning away real customers. - [Half of known disposable email domains no longer exist (October 2026 data)](https://disban.io/blog/half-of-disposable-email-domains-no-longer-exist): We looked up all 429,532 domains in Disban's disposable-email inventory. 52.1% no longer exist and only 40.5% can receive mail. Here is what that means for blocklists. - [Disposable email runs on shared mail infrastructure: what 8,522 mail operators tell us](https://disban.io/blog/disposable-email-infrastructure-cloudflare-mail-operators): Live disposable domains are spread across 8,522 mail operators, and 12.2% of them route through Cloudflare's free email forwarding. Why that makes domain-level evidence essential. - [How to block disposable emails at signup (with code)](https://disban.io/blog/block-disposable-emails-at-signup): Check the email domain on your server before creating the account, act on the category, and handle unknown results and outages without blocking real users. - [Disposable email vs email alias: make the right signup decision](https://disban.io/blog/disposable-email-vs-email-alias): Separate public inboxes, personal mail, and privacy relays before deciding which signups to accept. - [Gmail dots, plus tags, and the limits of email identity](https://disban.io/blog/gmail-dots-plus-tags-signup-limits): How to separate a delivery address from a limits identity without merging the wrong accounts. - [How much free credit can duplicate accounts unlock?](https://disban.io/blog/free-trial-referral-credit-exposure): Model the free allowance and referral reward together, then choose the controls that address the actual exposure. - [How to block disposable emails in a Next.js signup route](https://disban.io/blog/block-disposable-emails-nextjs): Reject Yopmail, Mailinator and other throwaway inboxes in a Next.js App Router route handler or Server Action with one call to Disban. Works without an API key. - [Block disposable emails in Next.js with Clerk](https://disban.io/blog/block-disposable-emails-nextjs-clerk): Turn on Clerk's free disposable-email block, then add a user.created webhook that checks each new account with Disban and bans throwaway inboxes. Works without an API key. - [Express middleware to block disposable and temporary email signups](https://disban.io/blog/block-disposable-emails-express): A drop-in Express middleware that rejects disposable and temporary email domains at registration, fails open on outages, and works without an API key. - [Reject disposable emails in a Python FastAPI signup endpoint](https://disban.io/blog/block-disposable-emails-python-fastapi): Use the disban package (standard library only) to reject disposable and temporary emails in FastAPI, Flask or Django signup code, with a keyless start and a fail-open default. - [An API that tells disposable, free and privacy-alias emails apart](https://disban.io/blog/api-disposable-free-or-alias-email): Disposable inbox, free provider like Gmail, or privacy relay like SimpleLogin? One API call returns which, so you can block throwaway inboxes without turning away real people. ## Free tools - [Free Disposable Email Checker](https://disban.io/tools/disposable-email-checker): Check whether an email address or domain is disposable, free webmail, a privacy alias or parked. Free live check, no signup, with its limits explained. - [CSV Email List Profiler](https://disban.io/tools/csv-email-profiler): Extract domains locally, remove duplicates, and inspect a small list without uploading anyone’s full email address. - [Signup Guard Generator](https://disban.io/tools/signup-guard-generator): Generate a server-side JavaScript integration with explicit decisions for disposable and unresolved results. - [Email Alias Explorer](https://disban.io/tools/email-alias-explorer): See which addresses group together under Disban's signup-limit policy. Keep delivery and identity separate. - [Signup Policy Lab](https://disban.io/tools/signup-policy-lab): Explore a decision before turning it into a signup rule. Personal inbox, relay, disposable, or unresolved? - [Free Credit Exposure Calculator](https://disban.io/tools/free-credit-calculator): See the combined effect of free accounts and referral rewards. Change the inputs, inspect the assumptions. ## Reference - [Methodology](https://disban.io/methodology): how domains are classified and what the evidence means - [Provider directory](https://disban.io/directory): disposable, free, alias and testing providers with their domains - [Support and corrections](https://disban.io/support): report a misclassified domain - [Why was my email address rejected?](https://disban.io/why): for people turned away at signup; sites can link it from their error message - [Full text of every guide](https://disban.io/llms-full.txt) --- # The best disposable email detection APIs in 2026, compared URL: https://disban.io/blog/best-disposable-email-detection-apis Published: 2026-10-13 Disban, UserCheck, Kickbox, ZeroBounce, Abstract API, DeBounce and open-source lists: free tiers, entry prices, what each checks, and which fits signup protection. | API | Free tier | Free check without a key | Paid entry | Checks the mailbox (SMTP) | Separates privacy aliases | Best for | |---|---|---|---|---|---|---| | Disban | 2,000 checks/month, no card | Yes: GET /api/v1/check, 30/day per network | Not yet on the website | No | Yes (alias category) | Signup decisions by category | | UserCheck | 1,000 credits/month, no card | Not stated | $50/month for 200,000 | Not documented | Yes (relay_domain) | Signup protection | | Kickbox | 100 verifications | Yes: open.kickbox.com | $5 for 500 | Yes | Not stated | Mailbox verification | | ZeroBounce | 100 credits/month | Not stated | $39 for 2,000 | Yes | Partly | List cleaning | | Abstract API | 100 requests/month | Not stated | $17/month, billed annually | Yes | Not stated | Simple all-in-one validation | | DeBounce | 100 credits, plus a free disposable endpoint | Yes: disposable.debounce.io | $15 for 5,000 | Yes (full validation) | Not stated | Free disposable lookups | | Open-source lists | Free | Not applicable: you host the list | None | No | No | Do-it-yourself, with your own upkeep | Vendor-stated facts as of 8 October 2026. Prices change; check each vendor's page. ## Which is the best disposable email detection API? For signup protection, the best choice is an API that checks the domain and tells you what kind of address it is, not just whether it is disposable. Disban and UserCheck both work this way and both separate privacy aliases from disposable inboxes. If you also need to confirm that each individual mailbox exists, for example before a marketing send, Kickbox, ZeroBounce, Abstract API and DeBounce verify mailboxes as well. A disclosure: we make Disban. We have included it, and we say plainly where other tools do something it does not. ## Domain checks vs mailbox verification There are two kinds of tools. Domain-level checks look at the part after the @ and classify it: disposable, free provider, alias, and so on. They are fast and do not contact the mailbox, which suits signup forms. Mailbox verification also connects to the recipient's mail server to ask whether the individual address exists. That suits cleaning a list before a campaign, but it is slower and some mail servers do not give a clear answer. ## 1. Disban: categories for signup decisions Disban checks the domain and returns one of six categories (disposable, free, alias, testing, parked or unknown) with the evidence behind it, plus a separate mail-routing check that catches typos and dead domains. It connects known domains with the mail servers they use and the operators that run them, so new disposable domains can be flagged on their first signup. You can try it with no key or signup: GET https://disban.io/api/v1/check/{email or domain} returns the category, a disposable flag and the mail-routing status (10 checks per hour and 30 per day per network). The disban package on npm and PyPI wraps the same call, and an MCP server at https://disban.io/mcp lets AI agents use it. The free plan adds 2,000 checks a month with full evidence, no card needed. It does not verify individual mailboxes, and it is in beta. ## 2. UserCheck: the closest alternative UserCheck is also domain-first. It returns separate fields for disposable domains, free email, privacy relays such as Apple Hide My Email and SimpleLogin, role accounts and mail records. The free plan includes 1,000 credits a month without a card, and paid plans start at $50 a month for 200,000 credits. Its documentation does not describe a mailbox (SMTP) check. ## 3. Kickbox: mailbox verification with a free disposable check Kickbox verifies individual mailboxes and returns flags for disposable, free, role and accept-all addresses, plus a quality score. It also runs a free domain-level disposable check at open.kickbox.com. New accounts get 100 free verifications, and credit packs start at $5 for 500. Its documentation does not describe a separate field for privacy aliases. ## 4. ZeroBounce: list cleaning and deliverability ZeroBounce is built for checking email lists before sending. Disposable is one of its sub-statuses, alongside spam traps, abuse, catch-all and role-based addresses, and it has a partial alias signal. The free plan includes 100 credits a month, and pay-as-you-go starts at $39 for 2,000 credits. It does not offer a domain-only lookup. ## 5. Abstract API: one endpoint for everything Abstract API's email validation endpoint returns format, free, disposable, role, catch-all, mail-record and SMTP checks with a quality score. The free plan includes 100 requests a month, and paid plans start at $17 a month billed annually. Privacy aliases are not documented as a separate signal. ## 6. DeBounce: a free disposable endpoint without a key DeBounce offers a free disposable check that needs no API key and returns true or false for an email or domain. Its exact rate limits are not published. Full validation, with result codes for disposable, accept-all and role addresses, starts at $15 for 5,000 credits, and new accounts get 100 free credits. ## 7. Open-source lists: free, but you maintain them Lists such as disposable-email-domains (CC0, updated daily) and 7c/fakefilter (BSD-3, removes domains after a year of inactivity) are free to use. They are only lists: you have to update them, match parent domains, and handle mistakes yourself. Lists also age. When we looked up the 429,532 domains in Disban's inventory in October 2026, 52.1% no longer existed. One widely used list, ivolo/disposable-email-domains, now says it is no longer maintained. ## Which disposable email APIs work without an API key? Three services answer a disposable check with no key: Disban, Kickbox's open.kickbox.com and DeBounce's disposable.debounce.io. Kickbox and DeBounce return true or false. Disban returns a category (disposable, free, alias, testing, parked or unknown) and a mail_routing status, so the same call also catches typo domains and domains that cannot receive mail. Treat null or unknown as unverified, not safe. Keyless endpoints are rate-limited; move to an API key for production signup traffic. ``` curl https://disban.io/api/v1/check/sharklasers.com # {"domain":"sharklasers.com","category":"disposable","disposable":true,"mail_routing":"routable"} // Node.js 18+, on your server const r = await fetch("https://disban.io/api/v1/check/" + encodeURIComponent(email)); const { disposable } = await r.json(); // true, false, or null when unknown ``` ## How to choose For signup forms, choose a domain-level API that separates disposable inboxes from free providers and privacy aliases, and tells you why it reached each result. For cleaning a list before a campaign, choose mailbox verification. For a hobby project with low traffic, a maintained open-source list can be enough. Whatever you choose, treat unknown as unknown rather than safe, and keep a way for real users to report a mistake. ## How we compiled this Every competitor fact comes from the vendor's own website, documentation or repository, read on 8 October 2026, not from review sites. Where a vendor's pages did not say something, we wrote not stated rather than guessing. Prices and plans change, so check each vendor's current page before deciding. --- # How to block disposable emails before sending with Resend (Node.js) URL: https://disban.io/blog/block-disposable-emails-before-sending-with-resend Published: 2026-10-13 Resend does not check whether an address is disposable. Check the domain with Disban first, then send the verification email with Resend only when the address is allowed. ## Does Resend block disposable email addresses? No. Resend sends to the address you give it. It protects your sender reputation by suppressing an address after a hard bounce or a spam complaint, but disposable inboxes accept mail by design, so they do not bounce and nobody complains. A verification email to a Yopmail or Mailinator address is delivered like any other. To keep disposable signups out, check the address before you call Resend. ## What you need A Resend API key in RESEND_API_KEY, a Disban API key in DISBAN_API_KEY (the free plan includes 2,000 checks a month; to try it first without a key, call GET https://disban.io/api/v1/check/{email}), and Node.js 18 or later, which has fetch built in. Install the Resend SDK with npm install resend. Run both calls on your server, never in the browser, so neither key is exposed. ## Step 1: check the domain with Disban Send the address to Disban before anything else. The helper returns a simple decision: block disposable and testing inboxes, ask the person to fix a domain that cannot receive mail, and allow everything else. If Disban is slow or unavailable, it allows the signup but marks the account so you can hold free credits until the email is confirmed. ``` // disban.js: classify the signup email before you send anything export async function checkSignupEmail(email) { try { const res = await fetch("https://disban.io/api/check", { method: "POST", headers: { Authorization: `Bearer ${process.env.DISBAN_API_KEY}`, "Content-Type": "application/json", }, body: JSON.stringify({ input: email }), signal: AbortSignal.timeout(3000), }); // An outage or limit should never lock real users out. if (!res.ok) return { action: "allow", holdCredits: true, reason: `disban_${res.status}` }; const result = await res.json(); if (result.mail_routing?.status === "invalid") return { action: "fix", reason: "no_mail_route" }; if (result.category === "disposable" || result.category === "testing") return { action: "block", reason: result.category }; return { action: "allow", holdCredits: result.category === "unknown", reason: result.category }; } catch { return { action: "allow", holdCredits: true, reason: "disban_unavailable" }; } } ``` ## Step 2: send the verification email only when allowed Call the helper first and stop if the decision is block or fix, with a clear message the person can act on. Otherwise send the email with Resend as usual. Resend returns data and error rather than throwing, so check error before continuing. ``` // signup.js: send the verification email with Resend only when the address is allowed import { Resend } from "resend"; import { checkSignupEmail } from "./disban.js"; const resend = new Resend(process.env.RESEND_API_KEY); export async function startSignup(email, code) { const decision = await checkSignupEmail(email); if (decision.action === "block") return { ok: false, error: "Please use a permanent email address." }; if (decision.action === "fix") return { ok: false, error: "This email domain can't receive mail. Check the address." }; const { data, error } = await resend.emails.send({ from: "Acme ", to: [email], subject: "Your verification code", html: `

Your code is ${code}.

`, }); if (error) return { ok: false, error: "We couldn't send the email. Please try again." }; // Store holdCredits with the account: grant free credits after the email is confirmed. return { ok: true, emailId: data.id, holdCredits: decision.holdCredits }; } ``` ## Step 3: wire it into your signup route In a Next.js App Router project, the route handler only needs to call startSignup and return the result. The same function works from Express, Fastify or a serverless function. ``` // app/api/signup/route.js (Next.js App Router) import { startSignup } from "@/lib/signup"; export async function POST(request) { const { email } = await request.json(); const code = String(Math.floor(100000 + Math.random() * 900000)); // use your own code store const result = await startSignup(email, code); return Response.json(result, { status: result.ok ? 200 : 400 }); } ``` ## Why this also helps deliverability Typos and dead domains, such as gmial.com or a lapsed disposable domain, produce hard bounces, and repeated hard bounces hurt your sender reputation with every mailbox provider. Disban's mail-routing check catches these before Resend sends anything, so the email never bounces in the first place. ## Handling unknown results, limits and outages Treat unknown as unknown: allow the signup and hold rewards rather than blocking. If Disban returns 429 (a limit) or 503 (mail routing could not be verified in time), the helper allows the signup with credits held; you can retry the check later in a background job. Never make signup depend on a third-party service being up. ## Test it Try sharklasers.com, which is disposable, gmail.com, which is a free provider, and a misspelled domain such as gmial.com, which cannot receive mail. You can check any domain in the browser with the free checker before writing code, and the full API reference is in the docs. --- # What is a disposable email address? URL: https://disban.io/blog/what-is-a-disposable-email-address Published: 2026-10-12 A disposable email address is a temporary inbox that works for minutes or days and is then abandoned. How they work, how they differ from free email and aliases, and how to recognise one. ## What is a disposable email address? A disposable email address is a temporary inbox that someone uses once, usually to get past a signup form, and then abandons. Services such as Yopmail, Mailinator and Guerrilla Mail hand out these addresses instantly, without registration, and many of their inboxes can be read by anyone who knows the address. The address works long enough to receive a verification email, then it is never used again. ## How does a disposable email address work? The service owns one or more domains and accepts mail for every possible address on them. When you type any name at that domain, the mail is stored and shown on the service's website. There is no account and no password. Most services delete messages after a few minutes or hours. Because the service controls the whole domain, it can offer unlimited addresses, and it can add new domains whenever signup forms start rejecting the old ones. ## Is a disposable email the same as a fake email? No. A fake email is an address that does not work at all, such as a typo or an invented domain. A disposable address really receives mail, which is why it passes a basic verification step. The difference matters for detection: a check that only asks whether the domain can receive mail will accept a disposable address, because it can. ## How is a disposable email different from Gmail or an email alias? Gmail, Outlook and Proton Mail are free email providers: the person owns a long-term inbox and keeps using it. Email aliases, such as SimpleLogin, Firefox Relay or DuckDuckGo addresses, forward mail to a real inbox the person keeps, so they protect privacy without disappearing. A disposable address is different from both: nobody owns it for the long term and it is not meant to be used again. Treating all three the same way blocks real customers. ## Why do people use disposable email addresses? Most people use them for ordinary reasons: to avoid marketing email, to read one article or download one file, or to test a product without handing over their real address. Some use them to abuse free tiers, creating new accounts to claim the same trial credits, referral bonuses or coupons again and again. The address itself does not tell you which one it is, so it is a signal about the signup, not proof about the person. ## How many disposable email domains are there? Disban's inventory contains 429,532 domains associated with disposable email services. When we looked them all up on 8 October 2026, only 40.5% could still receive mail and 52.1% no longer existed. Disposable services keep registering new domains and letting old ones lapse, so the number that matters is how many work today, not how many have ever been seen. ## How can you tell if an email address is disposable? Look at the domain, the part after the @. Check it against known disposable services, check which mail servers it uses, and check whether those servers belong to a disposable operator. Doing this by hand does not scale, so most products call an API at signup. Disban returns one of six categories (disposable, free, alias, testing, parked or unknown) with the evidence behind it, and you can try one domain at a time with the free checker without signing up. --- # How to detect disposable email addresses: five methods compared URL: https://disban.io/blog/how-to-detect-disposable-email-addresses Published: 2026-10-12 Blocklists, mail-server checks, operator matching, APIs and behaviour signals: what each method catches, what it misses, and which combination works at signup. ## What is the most reliable way to detect a disposable email? The most reliable way is to check the email's domain at signup against several kinds of evidence at once: known disposable domains, the mail servers the domain uses, and the operators behind those servers. Any single method misses something. A list misses new domains, and a mail-server check alone cannot tell a disposable inbox from a real company's mailbox. ## Method 1: a disposable domain blocklist A blocklist is a file of domains known to belong to disposable services. It is free, fast and easy to add. Its weakness is age: lists keep every domain they have ever seen. In our October 2026 lookups, 52.1% of 429,532 known disposable domains no longer existed, so a large part of any list is history. Lists also miss domains registered after the last update, and some public lists mix in free providers such as Gmail, which blocks real users. ## Method 2: check whether the domain can receive mail Looking up a domain's mail servers (its MX records) tells you whether mail can be delivered there right now. This catches typos and dead domains, such as gmial.com or a lapsed disposable domain. It does not catch working disposable services, because they receive mail by design. Use it as a separate check alongside the category, not instead of it. ## Method 3: match the mail servers and the operator behind them Disposable services register new domains constantly but tend to run them on mail servers they already operate. In our data, more than 400 separately registered domains route their mail to Yopmail's servers and more than 300 to Mailinator's. Recognising the operator lets you flag a new domain on its first signup, before any list includes it. The care needed: shared hosting and large mail platforms are used by legitimate companies too, so a shared server alone is not proof. ## Method 4: use a detection API An API combines the methods above, keeps the data current and returns a decision in one request. The trade-offs are a network call during signup and a dependency on another service, so set a short timeout and decide in advance what happens if the check is unavailable. A good API tells you why it reached a result, not only true or false, so you can handle edge cases such as privacy aliases. ## Method 5: behaviour signals Some abuse comes from real, permanent addresses. Signals such as many accounts from one network, repeated payment details, unusual signup speed or the same device across accounts catch what email checks cannot. They are a complement, not a replacement: email checks stop cheap, anonymous signups early, and behaviour signals catch the determined ones later. ## What does not work: keyword and pattern rules Rules such as rejecting domains that contain temp or mail, or rejecting cheap domain endings, both miss and harm. Many disposable domains have ordinary names, and millions of legitimate sites use endings such as .xyz or .click. In our data the most common ending among disposable domains is .com, used by 36.2% of them. ## Which combination should you use? At signup, check the domain with an API that combines lists, mail-server checks and operator matching, act on the category, and treat unknown as unknown rather than safe. Keep behaviour signals for the abuse that gets through. Review false positives with a simple correction process so real customers are never stuck. --- # Is Gmail a disposable email? Free email vs disposable email URL: https://disban.io/blog/is-gmail-a-disposable-email Published: 2026-10-12 No. Gmail, Outlook and Proton Mail are free email providers with long-term inboxes. Why some blocklists include them anyway, and how to treat free email at signup. ## Is Gmail a disposable email address? No. Gmail is a free email provider. Each Gmail address belongs to one account that its owner keeps using for years, with a password, recovery options and a long history. A disposable address is the opposite: nobody owns it for the long term and it is abandoned after one use. The same is true for Outlook, Yahoo, iCloud, Proton Mail and other free providers. ## Why do some blocklists include Gmail? Some public lists combine several kinds of domains in one file: free providers, disposable services and domains seen in spam or abuse. A file like that is useful for research, but using it as a signup blocklist rejects anyone with a Gmail or Outlook address, which for most consumer products is a large share of real customers. When you adopt a list, check what it contains before you block on it. ## Can people abuse free trials with Gmail? Yes, but differently. Creating a new Gmail account takes time and often a phone number, so it is slower than opening a disposable inbox. People also use Gmail dots and plus tags (for example j.doe+trial@gmail.com) to make one inbox look like several addresses. That is a duplicate-account problem rather than a disposable-email problem, and it is handled by normalising addresses, not by blocking the provider. ## What is the difference between free email and disposable email? Free email is a long-term inbox that costs nothing; disposable email is a temporary inbox meant to be thrown away. Free email providers verify accounts and keep them; disposable services accept mail for any name on their domains without accounts. For signup decisions, free email is usually allowed, while disposable email is blocked or allowed with limits such as no free credits. ## How should you treat free email addresses at signup? Allow them. If your product is for businesses and you prefer work addresses, ask for one politely or offer a benefit for using it, but do not reject free email outright: founders, freelancers and small teams often use Gmail. Normalise dots and plus tags if duplicate accounts are a concern, and keep strict rules for disposable domains. ## How Disban classifies free email Disban returns free for recognised consumer providers such as Gmail and Outlook, and these are protected from being classified as disposable even when they appear on a combined list. Disposable is reserved for temporary inbox services, alias for forwarding services, and unknown when there is not enough evidence. You can check any domain with the free checker. --- # How temporary email services work, and why new domains keep appearing URL: https://disban.io/blog/how-temporary-email-services-work Published: 2026-10-12 Temporary email services run many domains on the same mail servers and replace them as they get blocked. Our October 2026 data on Yopmail, Mailinator and generator.email shows the pattern. ## How does a temporary email service work? A temporary email service owns domains and runs mail servers that accept messages for any address on those domains. When a visitor picks an address, the service simply shows whatever mail arrives for it. There are no accounts, so creating an address costs the service nothing, and messages are deleted after a short time. ## Why do temporary email services use so many domains? Because signup forms block them. Once a domain appears on enough blocklists, its addresses stop working for the people using the service, so the service registers new domains and points them at the same mail servers. The domains change; the servers behind them mostly do not. ## How many domains share one service's mail servers? Hundreds. In Disban's DNS observations of 8 October 2026, more than 750 separately registered domains routed their mail to generator.email's servers, more than 400 to Yopmail's and more than 300 to Mailinator's. Some of these are the services' own alternate domains; others are domains registered by third parties and pointed at the service. Either way, mail for all of them ends up in the same place. ## Why do so many disposable domains stop working? Domains are cheap to register and cost money to renew, so services let blocked or unused ones lapse. Of 429,532 domains in Disban's inventory, 52.1% no longer existed when we looked them up in October 2026. A list that grows forever ends up mostly made of domains that are already gone. ## What does this mean for detection? Checking only a list of known domains is always behind, because the service has usually moved to a new domain by the time a list catches up. Checking the mail servers and the operator behind a domain catches new domains on their first use. The caution is that some mail infrastructure is shared with legitimate companies, so a match on shared hosting alone should not be treated as proof. ## How Disban uses this Disban connects the signals behind each signup: the domain itself, the mail servers it routes through, and the operator that runs them. Each result says which evidence matched, and counts on our site are published as rounded figures. You can see the clusters on the Disban homepage and check any domain with the free checker. --- # Should you block disposable email addresses? URL: https://disban.io/blog/should-you-block-disposable-emails Published: 2026-10-12 Usually yes for free trials and credits, but not always outright. When to block, when to allow with limits, and how to avoid turning away real customers. ## Should you block disposable email addresses? If your product gives away something valuable at signup, such as free credits, trials, referral rewards or coupons, blocking disposable addresses is usually worth it, because they make claiming that value again and again nearly free. If signup gives nothing away, you may prefer to allow them and simply not count them as real users. The right answer depends on what a new account can take. ## When should you block disposable emails? Block them when one person creating many accounts costs you money or skews results: credit-based products, free trials with paid third-party costs, referral programmes, coupons, giveaways, and community or marketplace signups where fake accounts harm others. Ask for a permanent address with a clear message rather than a vague error. ## When should you allow them? Allow them, perhaps with limits, when the account itself is harmless: newsletters, documentation, downloads and read-only tools. Some privacy-minded people use disposable inboxes for exactly these. A common middle path is to let the account in but withhold free credits until the person adds a permanent address. ## What about privacy email aliases? Treat them separately. Forwarding services such as SimpleLogin, Firefox Relay and DuckDuckGo addresses deliver mail to a real inbox the person keeps, so the account is reachable and long-lived. Blocking them mainly turns away privacy-conscious customers. Allow aliases, and if rewards are a concern, limit those rather than the signup. ## What is the risk of blocking too much? False positives. A rule that blocks a real company's domain, a free provider or a whole domain ending turns away paying customers, usually without you noticing. Act on clear categories, treat unknown as unknown rather than blocking it, and give people a way to report a mistake. ## A simple policy you can start with Disposable: ask for another address, or allow without credits. Testing inboxes: block in production. Free email and aliases: allow. Parked domains and domains that cannot receive mail: ask the person to check the address. Unknown: allow and flag for review. You can model this policy with the free signup policy lab before you build it. --- # Half of known disposable email domains no longer exist (October 2026 data) URL: https://disban.io/blog/half-of-disposable-email-domains-no-longer-exist Published: 2026-10-08 We looked up all 429,532 domains in Disban's disposable-email inventory. 52.1% no longer exist and only 40.5% can receive mail. Here is what that means for blocklists. ## What we measured Disban keeps an inventory of domains associated with disposable email services, built from public lists, provider inboxes and our own discovery. In the cycle that finished on 8 October 2026 we looked up the mail routing of every one of them: 429,532 domains. A domain counts as able to receive mail when it publishes mail servers (MX records) or, failing that, an address record that mail can fall back to. It counts as unable when the domain does not exist, publishes a null MX record, or has no route at all. ## The headline: most of the list is history 223,739 domains (52.1%) no longer exist in DNS at all. Another 11,046 still exist but cannot receive mail: 5,836 publish a null MX record, 4,136 have no mail route, and 1,074 point at mail servers without public addresses. Together that is 234,785 domains (54.7%) that cannot receive a verification email today. Only 174,013 domains (40.5%) can. The remaining 20,734 (4.8%) returned errors or timed out, so we do not count them either way. ## Why disposable domain lists rot Temporary email services register large numbers of cheap domains, use them until signup forms start rejecting them, and let them lapse. A list keeps every domain it has ever seen, so its size measures history, not current activity. A list of 400,000 domains can contain fewer than half that still work. That matters in two directions: list size is not the same as coverage, and a lapsed domain can be registered again by someone else. ## Providers behave very differently The pattern is not uniform. Of the 42,158 domains associated with tempm.com, only 8.4% can still receive mail and 89.6% are dead. For emailfake.com (34,038 domains) 23.5% are alive; for generator.email (14,009) 18.9%. At the other end, 95.9% of temp-mail.org's 2,845 domains still route mail. tempmail.lol, the largest provider in the inventory with 89,508 associated domains, is split almost evenly: 54.0% alive, 46.0% dead. Provider associations come from an imported inventory and are not independently verified; the mail-routing figures are our own lookups. ## Which domain endings they use .com is the most common ending by far, with 155,676 domains (36.2%), followed by .org (28,219), .click (24,039), .net (20,887), .cfd (17,641) and .tk (16,079). Low-cost endings such as .click, .cfd, .tk, .xyz and .site appear often, but they are also used by millions of legitimate sites. Blocking a whole ending would reject real customers and still miss the largest group, which uses .com. ## What this means for your signup checks Check the domain at the moment someone signs up instead of relying on a list snapshot. A domain that no longer exists cannot receive your verification email anyway, so the routing check catches typos and dead domains at the same time. Treat a domain that once appeared on a list but shows no current evidence as unknown rather than disposable, and keep a way to correct mistakes. The disposable domains that matter are the ones that work today. ## How Disban uses this data Every Disban check looks up mail routing live and returns it as a separate field from the category. Domains whose only evidence is an old list entry return unknown with historical_disposable set, so your own policy decides what to do with them. The full method, including how often evidence is renewed, is on the methodology page. --- # Disposable email runs on shared mail infrastructure: what 8,522 mail operators tell us URL: https://disban.io/blog/disposable-email-infrastructure-cloudflare-mail-operators Published: 2026-10-08 Live disposable domains are spread across 8,522 mail operators, and 12.2% of them route through Cloudflare's free email forwarding. Why that makes domain-level evidence essential. ## From domains to mail operators A disposable email service can own hundreds of domains, but every message still has to arrive at a mail server. We grouped the 174,013 domains in Disban's inventory that could receive mail on 8 October 2026 by the organisation that runs their mail servers. They are spread across 8,522 operators, and the ten largest handle 28.3% of the live domains. The rest is a long tail of small and self-hosted setups. ## The largest operator is a free forwarding service 21,229 live disposable domains (12.2%) receive mail through Cloudflare Email Routing, a free service that forwards mail for any domain using Cloudflare DNS. That is far more than any temporary-email company runs itself. The same service forwards mail for a very large number of legitimate businesses and personal sites, so the mail server alone says nothing about whether a domain is disposable. ## Some operators exist only for temporary email Behind Cloudflare, the next largest operators are dedicated to temporary inboxes: mimimail.me receives mail for 5,536 live domains, pigeonprotocol.com for 3,457, tempmail.tw for 3,415 and spymail.one for 2,785. When a service rotates to a brand-new domain, that domain usually points at the same mail servers. Recognising these dedicated servers lets a checker classify a new domain before it appears on any list. ## Parking and big providers show up too 3,370 live domains route to above.com, a domain-parking service, and 1,778 use Google's mail servers. Neither is evidence of disposable use on its own: parked domains rarely belong to an active inbox service, and Google hosts mail for millions of organisations. Rules that block a mail provider outright would reject large numbers of legitimate customers. ## One in five live domains has no MX record 34,747 of the live domains (20.0%) publish no MX record at all. They still receive mail because SMTP falls back to the domain's address record. A check that only looks for MX records would wrongly report these domains as unable to receive mail. ## What this means for detection Blocking by mail server catches rotating domains only when the server is dedicated to disposable email, and it causes false positives everywhere else. Blocking by domain ending does the same at a larger scale. Reliable detection combines exact domain evidence, mail servers that are known to be dedicated, and protection for shared providers such as Cloudflare, Google and parking services. That is the approach Disban's methodology describes, and it is why a shared platform never turns one tenant's behaviour into a verdict for everyone else. --- # How to block disposable emails at signup (with code) URL: https://disban.io/blog/block-disposable-emails-at-signup Published: 2026-10-08 Check the email domain on your server before creating the account, act on the category, and handle unknown results and outages without blocking real users. ## Why block disposable emails at signup A disposable address lets someone create an account they never intend to return to. The cost shows up later: free-trial credits claimed again and again, referral rewards farmed with throwaway inboxes, AI or API allowances drained by fresh accounts, and verification emails that bounce after the inbox expires. Checking the email domain once, when the account is created, is the cheapest point to stop that. It is also the point where a polite message such as "please use a permanent address" costs a real user the least. ## Where in the flow to check Run the check on your server, inside the request that creates the account, before you send a verification email or grant any credit. A browser-only check is easy to skip, and an API key in front-end code can be copied. Keep the check close to the insert: if two signups race, the second one should still be evaluated before it receives a reward. Disban only needs the domain; sending the full address is fine, but only the domain is used for classification. ## Try it without an API key To see the result before you sign up, call GET /api/v1/check with an email or domain. It needs no key and returns the category, a disposable flag (null when the domain is unknown) and the mail-routing status. It allows 10 checks per hour and 30 per day per network, so use it for prototypes and switch to the keyed call below for real signup traffic. The disban package on npm and PyPI makes the same call. ``` curl https://disban.io/api/v1/check/yopmail.com // Node.js 18+: block confirmed disposable domains const res = await fetch("https://disban.io/api/v1/check/" + encodeURIComponent(email)); const { disposable } = await res.json(); if (disposable === true) throw new Error("Please use a permanent email address."); ``` ## Call the API from your server Send the address to POST /api/check with your API key in the Authorization header. The response includes a category, a reason, the evidence that matched, and a separate mail_routing status. The same call works for a single address; POST /api/batch accepts up to 50 entries when you are reviewing an existing user list. ``` curl -X POST 'https://disban.io/api/check' \ -H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"input":"visitor@yopmail.com"}' ``` ## Decide what each category means for your product Act on the category, not on a single true/false flag. disposable: ask for a permanent address, or allow the account but withhold credits and rewards. free (Gmail, Outlook and other consumer mail): allow; most real people use these. alias (privacy relays such as SimpleLogin or Firefox Relay): allow; an alias forwards to a real inbox and is a privacy choice, not abuse. testing (inboxes built for QA): reject in production signup flows. parked: the domain is parked and is unlikely to receive mail, so ask the user to check the address. unknown: allow and flag for later review; unknown means there was not enough evidence, never that the address is safe. ## Check that the domain can receive mail Read mail_routing separately from the category. invalid means the domain has no current public mail route, which is usually a typo such as gmial.com, so ask the user to correct it. routable means a route exists; it does not prove that the mailbox exists or that the person owns it. Keep your normal email verification step for that. ## Node.js (Express or any server) A small helper that returns a decision you can store with the account. It treats a lookup failure as "allow but hold rewards" instead of rejecting the user. ``` async function checkSignupEmail(email) { const res = await fetch("https://disban.io/api/check", { method: "POST", headers: { Authorization: `Bearer ${process.env.DISBAN_API_KEY}`, "Content-Type": "application/json", }, body: JSON.stringify({ input: email }), signal: AbortSignal.timeout(4000), }); if (!res.ok) return { allow: true, holdRewards: true }; // 429 / 503: retry later const r = await res.json(); if (r.mail_routing?.status === "invalid") return { allow: false, message: "Check your email address." }; if (r.category === "disposable" || r.category === "testing") return { allow: false, message: "Please use a permanent email address." }; return { allow: true, holdRewards: r.category === "unknown" }; } ``` ## Next.js route handler Call the helper from the route that creates the account, never from client components, so the key stays on the server. ``` // app/api/signup/route.ts export async function POST(req: Request) { const { email, name } = await req.json(); const decision = await checkSignupEmail(email); if (!decision.allow) return Response.json({ error: decision.message }, { status: 422 }); const user = await createUser({ email, name, rewardsOnHold: decision.holdRewards }); await sendVerificationEmail(user); return Response.json({ ok: true }); } ``` ## Python (Django view) The same decision table in Python with requests. Keep the timeout short so a slow lookup never stalls signup. ``` import os, requests from django.http import JsonResponse def check_signup_email(email): try: r = requests.post("https://disban.io/api/check", headers={"Authorization": f"Bearer {os.environ['DISBAN_API_KEY']}"}, json={"input": email}, timeout=4) r.raise_for_status() except requests.RequestException: return {"allow": True, "hold_rewards": True} data = r.json() if data.get("mail_routing", {}).get("status") == "invalid": return {"allow": False, "message": "Check your email address."} if data["category"] in ("disposable", "testing"): return {"allow": False, "message": "Please use a permanent email address."} return {"allow": True, "hold_rewards": data["category"] == "unknown"} ``` ## Go A minimal client using the standard library. ``` type checkResult struct { Category string `json:"category"` MailRouting struct { Status string `json:"status"` } `json:"mail_routing"` } func checkSignupEmail(ctx context.Context, email string) (allow, holdRewards bool) { body, _ := json.Marshal(map[string]string{"input": email}) req, _ := http.NewRequestWithContext(ctx, "POST", "https://disban.io/api/check", bytes.NewReader(body)) req.Header.Set("Authorization", "Bearer "+os.Getenv("DISBAN_API_KEY")) req.Header.Set("Content-Type", "application/json") res, err := (&http.Client{Timeout: 4 * time.Second}).Do(req) if err != nil || res.StatusCode != http.StatusOK { return true, true } defer res.Body.Close() var r checkResult if json.NewDecoder(res.Body).Decode(&r) != nil { return true, true } if r.MailRouting.Status == "invalid" || r.Category == "disposable" || r.Category == "testing" { return false, false } return true, r.Category == "unknown" } ``` ## Handle outages and limits without blocking real users Two responses need a plan. 503 with code verification_unavailable means mail routing could not be verified in time; no credit is charged and the response carries Retry-After. 429 means you reached your plan or per-second limit. In both cases, do not reject the user and do not treat the address as clean. Create the account, hold free credits or referral rewards, and re-check in the background before releasing them. ## Write a message people can act on Tell people what to do, not what you suspect: "Please use a permanent email address. Temporary inboxes can't receive account notices." Avoid accusing language, and give a route to support for mistakes. Disban accepts domain corrections with evidence, and a reviewed correction applies to new checks. ## Measure the rule after launch Log the category and decision for each signup, without storing more of the address than you need. Compare completion rates, support requests and later activity by category. If unknown or alias users behave like everyone else, keep allowing them. If a pattern of abuse appears, tighten the rule for rewards first, not for access. --- # Disposable email vs email alias: make the right signup decision URL: https://disban.io/blog/disposable-email-vs-email-alias Separate public inboxes, personal mail, and privacy relays before deciding which signups to accept. ## Start with the mailbox model An address string does not explain how its inbox works. A personal mailbox, a public testing inbox, and a forwarding alias may all receive a verification message. They still represent different product decisions. Classifying them together makes a rule easier to write, but harder to justify to legitimate customers. ## A relay has a useful job SimpleLogin describes a service that forwards messages from an alias to a chosen mailbox. That extra address helps its owner keep an underlying inbox private. Receiving mail through a relay is therefore not, by itself, evidence of abuse. It also does not establish that two aliases belong to different people. Both points matter when you issue signup rewards. ## Separate access from the reward Decide which capability needs protection. Reading a product tutorial, consuming a costly free allowance, and claiming a referral reward need not use the same gate. You can verify ownership for account access and apply independent limits to rewards. Make that distinction visible in the interface: explain whether you need another address, a completed verification, or a later attempt. ## Make uncertainty an explicit state A classification service may be temporarily unable to resolve a domain. Do not convert that failure into a claim that the address is safe or disposable. Keep the result unresolved, explain the retry, and avoid issuing a reward while the required check is incomplete. A policy should define this path before the first upstream outage. ## Measure the cost of your rule Compare completed signups, verification failures, appeals, and later product use across address categories. Review mistaken rejections alongside apparent abuse. A lower signup count is not evidence of better customers. Begin with a documented policy, retain a way to correct classifications, and revise the policy when observed behavior supports it. --- # Gmail dots, plus tags, and the limits of email identity URL: https://disban.io/blog/gmail-dots-plus-tags-signup-limits How to separate a delivery address from a limits identity without merging the wrong accounts. ## Delivery and limits solve different problems Your delivery address answers where to send a message. A limits identity answers which addresses your anti-abuse policy groups together. Store those concepts separately. Rewriting a customer's delivery address to match a deduplication rule can change login expectations and make later support work confusing. ## Apply provider rules narrowly Google says dots do not distinguish consumer Gmail addresses. Its documentation also explicitly says dots matter for work, school, or organization addresses. So a rule that removes dots from every address, or every domain hosted by Google, goes beyond that documented behavior. Preserve custom-domain dots unless you have a justified, provider-specific rule. ## Plus stripping is a policy choice Disban's signup-limit policy strips a plus suffix and groups Gmail and Googlemail spellings. The alias explorer makes that policy visible. On custom domains, plus stripping is an anti-abuse assumption, not proof of equivalent delivery. Some mail systems can use different addressing rules. Explain this tradeoff and keep a route for legitimate account-access problems. ## Enforce the rule where accounts are created A check performed only when a verification email is requested is incomplete. Two requests can receive codes before either creates an account. Recheck the identity inside the transaction that inserts the user. Keep normal authentication tied to the stored address; a shared limits identity must not become permission to log in as another account. ## Know what normalization cannot do Different catch-all addresses, separate mailboxes, and independent relay aliases can still belong to one person. Deleting an account can also change what history is available for limits. Canonicalization closes a specific class of duplicate-string problems. It does not prove personhood. Protect valuable rewards with atomic grants, explicit caps, and a documented deletion policy as well. --- # How much free credit can duplicate accounts unlock? URL: https://disban.io/blog/free-trial-referral-credit-exposure Model the free allowance and referral reward together, then choose the controls that address the actual exposure. ## Count the whole incentive A referral reward can be the visible incentive while the new account's ordinary allowance is the larger exposure. Model both. For N additional accounts, an allowance of F credits, a referral reward of R credits, and a reward cap of C, the simple monthly upper bound is N × F + min(N, C) × R. That assumes every extra account qualifies and all credits can be used. ## Use an example, not a forecast With 10 hypothetical additional accounts, 2,000 credits per account, a 100-credit reward, and a cap of 10 rewards, the model yields 21,000 credits: 20,000 in ordinary allowances and 1,000 in rewards. These are illustrative inputs, not an estimate of actual abuse or a promise that prevention would recover that amount. ## Make your assumptions visible The calculator intentionally ignores identity checks, domain caps, expiry, request rates, and credit consumption. That makes it useful as a starting upper-bound model. Your realized cost also depends on marginal cost per successful check. List price is not necessarily your operating cost. Keep credit exposure and money separate unless you have reliable cost data. ## Protect the grant, not just the button The server needs to decide eligibility and record a reward once. Repeated requests, concurrent verification, or account deletion must not silently create another eligible claim. A UI message or a disabled share button cannot provide that guarantee. Preserve enough purpose-limited state to enforce the policy, and disclose what remains after deletion. ## Change one policy at a time Possible controls include account-identity limits, a referrer cap, a per-domain reward cap, or a later activation milestone. Each has a cost: a strict shared-domain cap can affect unrelated customers using a popular provider. Choose controls around the exposure you actually have, measure legitimate conversion, and document the reward trigger so customers are not surprised. --- # How to block disposable emails in a Next.js signup route URL: https://disban.io/blog/block-disposable-emails-nextjs Published: 2026-10-19 Reject Yopmail, Mailinator and other throwaway inboxes in a Next.js App Router route handler or Server Action with one call to Disban. Works without an API key. ## How do I block disposable emails in Next.js? Check the email on the server, inside the route handler or Server Action that creates the account, before you send a verification email. Install the disban package, call signupDecision(email), and stop when the action is block (a disposable or test inbox) or fix (a domain that cannot receive mail). It needs no API key to start, has no dependencies, and runs on the Node.js and Edge runtimes. ## Try it first, without a key The package calls Disban's keyless endpoint, so you can see a real answer before signing up for anything. ``` npm install disban curl https://disban.io/api/v1/check/yopmail.com # {"domain":"yopmail.com","category":"disposable","disposable":true,"mail_routing":"routable"} ``` ## App Router route handler Put the check at the top of the POST handler. Return a message the person can act on, rather than an accusation. ``` // app/api/signup/route.ts import { signupDecision } from "disban"; export async function POST(request: Request) { const { email } = await request.json(); const d = await signupDecision(email); if (d.action === "block") return Response.json({ error: "Please use a permanent email address." }, { status: 400 }); if (d.action === "fix") return Response.json({ error: "This email domain can't receive mail. Check the address." }, { status: 400 }); // d.action === "allow". d.hold is true for unknown domains or when Disban was unreachable: // create the account, but hold free credits until the email is confirmed. const user = await createUser({ email, holdCredits: d.hold }); return Response.json({ ok: true, id: user.id }); } ``` ## Server Action version The same call works in a Server Action, which is common for signup forms built with useActionState. ``` // app/signup/actions.ts "use server"; import { signupDecision } from "disban"; export async function signUp(_: unknown, form: FormData) { const email = String(form.get("email") ?? ""); const d = await signupDecision(email); if (d.action === "block") return { error: "Please use a permanent email address." }; if (d.action === "fix") return { error: "This email domain can't receive mail. Check the address." }; await createUser({ email, holdCredits: d.hold }); return { ok: true }; } ``` ## Production: add a free API key The keyless endpoint allows 10 checks per hour and 30 per day per network; set DISBAN_API_KEY (free, 2,000 checks a month, no card) and the same code switches to the keyed API with full evidence. Add it in your hosting provider's environment variables (Vercel: Project Settings, Environment Variables) and never expose it to the browser: do not prefix it with NEXT_PUBLIC_. ``` npx disban signup # name, email, 6-digit code: prints your key # .env.local DISBAN_API_KEY=dbn_... ``` ## What it blocks and what it lets through Disban classifies the domain into one of six categories. block covers disposable and testing inboxes. Free providers such as Gmail and Outlook are allowed. Privacy relays such as SimpleLogin, Firefox Relay and Apple Hide My Email are category alias and are allowed by default, because a real person reads them. Domains with no working mail route return fix, which also catches typos like gmial.com before your verification email bounces. ## Handling unknown results and outages signupDecision never locks real users out. If Disban is slow, rate-limited or unreachable it returns allow with hold: true, so you can create the account but hold free credits or rewards until the email is confirmed. Do not run the check in middleware for every request: one call per signup is enough, and middleware would spend your quota on page views. --- # Block disposable emails in Next.js with Clerk URL: https://disban.io/blog/block-disposable-emails-nextjs-clerk Published: 2026-11-12 Turn on Clerk's free disposable-email block, then add a user.created webhook that checks each new account with Disban and bans throwaway inboxes. Works without an API key. ## How do I block disposable emails with Clerk in Next.js? Do two things. First turn on Clerk's own disposable-email protection, which is free on every plan and off by default. Then add a user.created webhook that checks each new account's email with Disban and bans the account when the domain is disposable or a testing inbox. The webhook runs on your server, so it can't be skipped by someone calling Clerk directly from a script, and it needs no API key to start. ## Start with Clerk's own setting Clerk includes a "Block disposable email addresses" protection on every plan. It is off by default, so check your dashboard's protection settings. It blocks domains Clerk already knows are disposable, at sign-up and when someone adds an email to an existing account; it doesn't affect sign-in. A broader "Block risky email domains" protection needs Clerk's Business plan. Disban adds what a fixed list can't: new domains on mail servers known to run disposable inboxes, domains that can't receive mail at all, and an unknown category you can hold rather than block. Every answer also says why. ## The webhook: the check that can't be skipped In the Clerk dashboard, add a webhook endpoint for user.created pointing at this route, and put its signing secret in CLERK_WEBHOOK_SIGNING_SECRET. If your middleware protects routes, leave /api/webhooks public: webhooks carry no session. Clerk sends user.created once the sign-up is complete, so the address has already received the verification code; banning signs the account out and stops it signing in again. ``` npm install disban // app/api/webhooks/clerk/route.ts import { verifyWebhook } from "@clerk/nextjs/webhooks"; import { clerkClient } from "@clerk/nextjs/server"; import type { NextRequest } from "next/server"; import { signupDecision } from "disban"; export async function POST(req: NextRequest) { let evt; try { evt = await verifyWebhook(req); // reads CLERK_WEBHOOK_SIGNING_SECRET } catch { return new Response("Invalid signature", { status: 400 }); } if (evt.type !== "user.created") return new Response("ok"); const user = evt.data; const email = user.email_addresses.find((e) => e.id === user.primary_email_address_id)?.email_address; if (!email) return new Response("ok"); const d = await signupDecision(email); const clerk = await clerkClient(); if (d.action === "block") { await clerk.users.banUser(user.id); } else if (d.action === "allow" && d.hold) { // unknown domain, or Disban was unreachable: keep the account, hold free credits until you trust it await clerk.users.updateUserMetadata(user.id, { privateMetadata: { holdCredits: true } }); } return new Response("ok"); } ``` ## A friendlier message on a custom sign-up form With Clerk's prebuilt SignUp component, the webhook is the whole integration. If you built your own form with useSignUp, you can also check the address before calling signUp.create, so people see a clear message instead of a banned account. Keep the webhook as well: the browser talks to Clerk directly, so this check is for the message, not for security. ``` // app/sign-up/check-email.ts "use server"; import { signupDecision } from "disban"; export async function checkEmail(email: string) { const d = await signupDecision(email); if (d.action === "block") return "Please use a permanent email address."; if (d.action === "fix") return "This email domain can't receive mail. Check the address."; return null; } // in your sign-up form, just before your existing signUp.create(...) call const problem = await checkEmail(emailAddress); if (problem) return setError(problem); ``` ## Production: add a free API key The keyless endpoint allows 10 checks per hour and 30 per day per network, which is enough to try this but not for real sign-up traffic. Set DISBAN_API_KEY (free, 2,000 checks a month, no card) in your hosting provider's environment variables and the same code uses the keyed API with full evidence. Never prefix it with NEXT_PUBLIC_. ``` npx disban signup # name, email, 6-digit code: prints your key # .env.local DISBAN_API_KEY=dbn_... CLERK_WEBHOOK_SIGNING_SECRET=whsec_... ``` ## What gets blocked, and what doesn't signupDecision blocks the disposable and testing categories. Free providers such as Gmail and Outlook are allowed, and so are privacy relays such as SimpleLogin, Firefox Relay and Apple Hide My Email (category alias), because a real person reads them. fix means the domain has no working mail route; on the webhook it rarely happens, because Clerk has already delivered a code to the address. ## When Disban is slow or down signupDecision never locks real people out. If Disban is slow, rate-limited or unreachable, it returns allow with hold set to true, so the account is created and the webhook marks it to hold free credits. Clerk retries webhooks that fail, so return 200 once you've handled the event, even when you chose to do nothing. --- # Express middleware to block disposable and temporary email signups URL: https://disban.io/blog/block-disposable-emails-express Published: 2026-10-19 A drop-in Express middleware that rejects disposable and temporary email domains at registration, fails open on outages, and works without an API key. ## How do I block temporary email domains in Express? Add a middleware to your registration route that reads req.body.email, calls signupDecision from the disban package, and responds with 400 when the action is block or fix. Allowed requests continue to your handler with the decision attached, so the handler can hold free credits for unknown domains. No API key is needed to start. ## Install and try it Node.js 18 or later is enough; the package has no dependencies. ``` npm install disban curl https://disban.io/api/v1/check/mailinator.com # {"domain":"mailinator.com","category":"disposable","disposable":true,"mail_routing":"routable"} ``` ## The middleware Mount it only on the routes that create accounts, after express.json(). ``` // blockDisposable.js import { signupDecision } from "disban"; export async function blockDisposable(req, res, next) { const email = req.body?.email; if (typeof email !== "string") return res.status(400).json({ error: "Email is required." }); const d = await signupDecision(email); if (d.action === "block") return res.status(400).json({ error: "Please use a permanent email address." }); if (d.action === "fix") return res.status(400).json({ error: "This email domain can't receive mail. Check the address." }); req.signup = d; // d.hold: true for unknown domains or when Disban was unreachable next(); } // app.js import express from "express"; import { blockDisposable } from "./blockDisposable.js"; const app = express(); app.use(express.json()); app.post("/register", blockDisposable, async (req, res) => { const user = await createUser({ email: req.body.email, holdCredits: req.signup.hold }); res.json({ ok: true, id: user.id }); }); ``` ## Production: add a free API key The keyless endpoint allows 10 checks per hour and 30 per day per network; set DISBAN_API_KEY (free, 2,000 checks a month, no card) and the same code switches to the keyed API with full evidence. ``` npx disban signup export DISBAN_API_KEY=dbn_... ``` ## Why not a static list of domains? Open-source lists only know domains someone has already added, and they age: when we looked up the 429,532 domains in Disban's inventory in October 2026, 52.1% no longer existed. Disban also checks where a domain's mail goes and which operator runs those mail servers, so a brand-new domain on a known disposable operator is caught on its first signup, and every answer says why. ## Handling unknown results and outages signupDecision never locks real users out. If Disban is slow, rate-limited or unreachable it returns allow with hold: true, so you can create the account but hold free credits or rewards until the email is confirmed. --- # Reject disposable emails in a Python FastAPI signup endpoint URL: https://disban.io/blog/block-disposable-emails-python-fastapi Published: 2026-10-19 Use the disban package (standard library only) to reject disposable and temporary emails in FastAPI, Flask or Django signup code, with a keyless start and a fail-open default. ## How do I reject disposable emails in FastAPI? Install disban with pip, call signup_decision(email) in the signup endpoint, and raise HTTPException(400) when the action is block or fix. The package uses only the Python standard library and needs no API key to start. The same function works in Flask, Django or any other Python code. ## Install and try it Python 3.8 or later. ``` pip install disban python -c "from disban import is_disposable; print(is_disposable('someone@sharklasers.com'))" # True ``` ## FastAPI endpoint signup_decision makes a blocking HTTP call, so declare the endpoint with def (FastAPI runs it in a worker thread) or wrap the call in run_in_threadpool from an async endpoint. ``` # main.py from fastapi import FastAPI, HTTPException from pydantic import BaseModel, EmailStr from disban import signup_decision app = FastAPI() class Signup(BaseModel): email: EmailStr @app.post("/signup") def signup(body: Signup): d = signup_decision(body.email) if d["action"] == "block": raise HTTPException(400, "Please use a permanent email address.") if d["action"] == "fix": raise HTTPException(400, "This email domain can't receive mail. Check the address.") # d["hold"] is True for unknown domains or when Disban was unreachable user = create_user(body.email, hold_credits=d["hold"]) return {"ok": True, "id": user.id} ``` ## Production: add a free API key The keyless endpoint allows 10 checks per hour and 30 per day per network; set DISBAN_API_KEY (free, 2,000 checks a month, no card) and the same code switches to the keyed API with full evidence. ``` disban signup # or: python -m disban signup export DISBAN_API_KEY=dbn_... ``` ## Handling unknown results and outages signup_decision never locks real users out. If Disban is slow, rate-limited or unreachable it returns allow with hold set to True, so you can create the account but hold free credits or rewards until the email is confirmed. --- # An API that tells disposable, free and privacy-alias emails apart URL: https://disban.io/blog/api-disposable-free-or-alias-email Published: 2026-10-19 Disposable inbox, free provider like Gmail, or privacy relay like SimpleLogin? One API call returns which, so you can block throwaway inboxes without turning away real people. ## Is there an API that tells disposable, free and alias emails apart? Yes. Disban classifies the domain of an email address into one of six categories: disposable (throwaway inboxes such as Yopmail or Mailinator), free (permanent free providers such as Gmail, Outlook and Proton Mail), alias (privacy relays such as SimpleLogin, Firefox Relay and Apple Hide My Email), testing (developer test inboxes such as Mailosaur), parked, or unknown. It also reports whether the domain can receive mail at all. You can try it with no key or signup. ``` curl https://disban.io/api/v1/check/yopmail.com # {"domain":"yopmail.com","category":"disposable","disposable":true,"mail_routing":"routable"} curl https://disban.io/api/v1/check/gmail.com # {"domain":"gmail.com","category":"free","disposable":false,"mail_routing":"routable"} ``` ## Why the three are different signals A disposable inbox is public or short-lived: anyone can read it, and it will not be there next month, so it suits people who want a free trial without an account. A free provider is a permanent personal mailbox, and most of your real users have one. A privacy alias forwards to a person's real inbox and hides the address; the person reads your mail and can reply, they just do not want to share their main address. Treating aliases as disposable turns away privacy-minded customers, which is why a yes/no disposable flag is not enough. ## What to do with each category Block disposable and testing. Allow free. Allow alias by default, or require extra verification if your product hands out something valuable at signup. For unknown, allow the signup but hold free credits until the email is confirmed: unknown means there is not enough evidence either way, not that the domain is safe. For domains that cannot receive mail, ask the person to check the address. ## In code The disban package for Node.js and Python wraps this policy as signupDecision / signup_decision, returning block, fix or allow. ``` // npm install disban import { check } from "disban"; const r = await check("someone@simplelogin.com"); // r.category === "alias": a real person behind a relay # pip install disban from disban import check check("someone@outlook.com")["category"] # "free" ``` ## How the categories are decided Disban first matches the domain against curated catalogs of free providers, relay services and testing tools, then its disposable inventory, then the mail servers the domain uses and the operators behind them, and finally a live mail-routing check. Every answer includes the reason and the evidence that matched, so a decision can be explained to the person it affects. Free API keys add 2,000 checks a month and batch requests of up to 50.