Skip to content
Get a quote

Supabase Auth errorSupabase: “Email address is invalid” (email_address_invalid)

Sign-up or a magic link fails with Email address "…" is invalid, error code email_address_invalid, even though the address looks fine. Supabase Auth refuses some addresses before it sends any email, and test addresses are the first on its list. Here’s what it rejects, in Supabase’s words, and how to tell it apart from the default email service’s own limit, or hand it over at a fixed price.

Short answer

Supabase Auth refuses example and test domains, so test@example.com or a .test address fails on purpose. Test with a real inbox you control. If a real customer’s address is refused, check for a typo in the domain and that the domain can receive mail. If the error says Email address not authorized instead, that is the default email service’s team-only limit: set up custom SMTP.

Why the address is refused

  1. 01

    A test or example address

    “Example and test domains are currently not supported. Use a different email address.” Supabase, Auth error codes

    Addresses on example.com, test.com, .test, .example, .local and similar reserved names are refused, as are a few test addresses people type often. Use a real inbox for testing, or a plus address on your own domain.

  2. 02

    A typo in the domain

    Supabase Auth’s open-source code also refuses common misspellings of big email domains, such as gamil.com. Show people the address back with a short hint to check it, rather than the raw error.

  3. 03

    The domain can’t receive mail

    Supabase Auth’s code can also check that the domain has mail servers set up. A new company domain without mail records, or a misspelled one, fails this way. Check the domain’s MX records before suspecting the app.

  4. 04

    Not the same as “Email address not authorized”

    “Unless you configure a custom SMTP server for your project, Supabase Auth will refuse to deliver messages to addresses that are not part of the project's team.” Supabase, Send emails with custom SMTP

    If the message says not authorized, the address is fine: the project is still on Supabase’s default email service, which only sends to team members. Set up custom SMTP before launch.

Checked against the vendor’s docs on : Supabase docs: Auth error codes; Supabase docs: Send emails with custom SMTP.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: Supabase auth emails going to spam · Supabase email rate limit exceeded · Supabase Signups not allowed for this instance · Supabase Email link is invalid or has expired

Questions

More on this error

Can I turn this check off?

Not for example and test domains: those can never receive mail, so the sign-up could never be confirmed. Use a real inbox for testing. For automated tests, use addresses at a domain you control.

A real customer’s address is refused. What do you need from me?

The exact address or at least its domain, and the time it failed. The Auth logs in the Supabase dashboard show the refused request.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.

Describe your problem All fixes