Description
Ensure any custom domain configured for the project, such as api.example.com, has completed DNS verification and SSL certificate issuance and has been activated. Domains should not be left in a pending or failed state, and unused custom domain setups should be removed.
Rationale
A custom domain that is not fully verified may not have a valid SSL certificate, causing errors or insecure connections for users. Pending setups with DNS records left in place can also create confusion or be taken over later. Completing verification and activation makes sure the domain serves traffic securely with a valid certificate.
Impact
The custom domain serves traffic with a valid SSL certificate
Avoids broken or insecure connections for users
Auth and OAuth settings may need updating after activation
Default Value
Custom domains are a paid add-on. After a domain is added, it stays pending until its DNS records are verified and it is activated.
Pre-Requisites
Project Owner or Admin role
Custom Domain add-on
Access to the domain's DNS settings
Supabase CLI for reverify and activate commands
Test Plan
Sign in to the Supabase Dashboard at https://supabase.com/dashboard.
Select your project.
Open Project Settings and select General, then go to the Custom Domains section.
Verify that the custom domain shows as active with a verified certificate.
If it shows pending or failed, follow the implementation steps.
Implementation Steps
In your DNS provider, confirm the CNAME record points to your project's supabase.co domain and that the TXT verification records are added exactly as shown.
Run: supabase domains reverify --project-ref <project-ref>
When verification succeeds, run: supabase domains activate --project-ref <project-ref>
Check the Custom Domains section again and confirm the domain is active.
Backout Plan
Run: supabase domains delete --project-ref <project-ref> to remove the custom domain.
Remove the related CNAME and TXT records from your DNS provider.
Reference