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 <onboarding@your-domain.com>",
to: [email],
subject: "Your verification code",
html: `<p>Your code is <strong>${code}</strong>.</p>`,
});
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.
Source for provider behavior: Resend: Email Suppressions. Product-policy guidance is Disban's interpretation.