Fix guide · updated 2026-11-13
Resend "You can only send testing emails to your own email address": the fix
You can only send testing emails to your own email address (you@example.com). To send emails to other recipients, please verify a domain at resend.com/domains, and change the `from` address to an email using this domain.
Your app's emails work when you test them, then nobody else gets them: sign-up confirmations, invites, order emails. In the Resend logs, or in your function's logs, each failed send says 403 and You can only send testing emails to your own email address. Nothing is wrong with your code. You're sending from Resend's shared test address, and that address can only write to you.
What the error means
Every new Resend account can send from onboarding@resend.dev right away, with no setup. Resend's own examples use it, so code written by AI builders often does too. But resend.dev is for testing only: Resend delivers those emails only to the address your Resend account was created with. That's why everything works when you test with your own email, and fails for every real user.
The fix has two parts: verify a domain you own in Resend, then change the from address in your app to an address on that domain.
1. Verify your domain in Resend
- In Resend, open Domains → Add Domain. Resend recommends a subdomain such as
updates.yourapp.comrather thanyourapp.comitself, to keep your sending reputation separate. - Pick the region closest to most of your users.
- Open the domain's Records tab. Add each record (DKIM and SPF:
TXT, plusMXorCNAME) wherever your domain's DNS is managed: Cloudflare, GoDaddy, Namecheap, or the company you bought it from. Copy and paste the values: they must match exactly. - On Cloudflare, set any
CNAMEfrom Resend to DNS only (grey cloud), not proxied. Resend's docs warn about this. - Wait for the status to turn Verified. Resend says it often takes about 15 minutes, but DNS changes can take up to 72 hours to spread. Still pending after 72 hours? Check that the records are visible with Resend's dns.email tool, then press Restart verification.
2. Change the from address in your app
Once the domain is verified, any address on it works as a sender with no extra setup, like hello@updates.yourapp.com. Now find where your app sets from:
- Lovable, Bolt and other apps on Supabase: it's in an edge function, usually
supabase/functions/<name>/index.ts, in theresend.emails.send({ from: … })call. Replaceonboarding@resend.devwith your new address. You can keep a name in front:Your App <hello@updates.yourapp.com>. Then make sure the new version is deployed (with the Supabase CLI:supabase functions deploy <name>). - Next.js, Node or another server: search your code for
resend.dev. If the sender comes from an environment variable, change it where the app is hosted too (Vercel, Netlify, Railway…), then redeploy. - Supabase sign-up and password emails sent through Resend's SMTP: the sender address is in Supabase → Authentication → SMTP Settings, and it must be on the verified domain too. If those emails fail with "Error sending confirmation email", see our guide to Supabase "Error sending confirmation email".
3. The domain is verified, but sending still fails
403The yourapp.com domain is not verified: the domain infromisn't exactly the one you verified. If you verifiedupdates.yourapp.com, an address at plainyourapp.comis refused. Use an address on the verified subdomain, or verify the other domain too.- Still the same testing-email error: the deployed code still sends from
onboarding@resend.dev. Resend → Logs shows each request with thefromit received, so you can see which version is running. 429You have exceeded your daily email sending quota: a plan limit, not a setup problem. It resets at midnight UTC, or you can upgrade the plan. Resend counts both sent and received emails.422when testing with@example.comor@test.comaddresses: Resend blocks them because they bounce. Use Resend's test addresses instead, such asdelivered@resend.dev(a delivered email) orbounced@resend.dev(a bounce).
Still stuck?
Resend → Logs shows every request your app made, with its status code and error. If your request isn't there at all, the email never left your app: check your function's logs, and see our guide to "Edge Function returned a non-2xx status code".
Other Supabase problems? See Supabase fixes.