Verify Domain keeps faliing

Get Help
1

DNS verification:
Google DNS (8.8.8.8) resolves CNAME correctly
Cloudflare DNS (1.1.1.1) resolves CNAME correctly

Management API:
status = pending_verification
verification.status = pending

returns HTTP 200, but domain remains pending_verification.

No verification.error_msg is returned.arching for your answer.

3

Hi @girishbedekar

Welcome to the Auth0 Community!

Your Auth0 custom domain verification is stuck in pending_verification status despite the CNAME record resolving correctly via multiple DNS resolvers (Google DNS and Cloudflare DNS). The Management API returns HTTP 200 with status = pending_verification and verification.status = pending, but no error message is provided, and the verification does not progress.

Auth0’s custom domain verification process can take up to 48 hours to complete, even when the CNAME record is correctly configured and resolves via external DNS tools. However, if verification remains stuck beyond 48 hours with no error message, this indicates a potential issue with Auth0’s internal verification process that requires investigation by Auth0 Support.

[ROOT CAUSE]

Auth0’s custom domain verification involves two separate processes:

  1. DNS propagation: Your CNAME record must propagate globally across DNS resolvers. This typically takes 15 minutes to a few hours, but can take up to 48 hours in rare cases.

  2. Auth0 verification polling: After DNS propagation, Auth0’s verification service must detect and validate your CNAME record. This polling process can experience delays due to DNS caching, Auth0-side polling intervals, or internal service delays.

The fact that your CNAME resolves correctly via Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) indicates that DNS propagation is complete. However, Auth0’s verification service may be experiencing one of the following issues:

  • Auth0-side DNS caching: Auth0’s verification service may be caching an older DNS state and not detecting the newly-added CNAME record.
  • Verification service polling delay: Auth0’s verification service may not have polled your DNS record yet, or may be experiencing a delay in its polling cycle.
  • Tenant-level restriction: In rare cases, tenant-level settings or account restrictions may prevent verification from completing.
  • Duplicate CNAME records: If your DNS provider allows multiple CNAME records with the same name, having duplicates can cause verification to fail.

[Recommended Troubleshooting Steps]

Step 1: Verify CNAME configuration (confirm no duplicates)

  1. Log in to your DNS provider’s dashboard.
  2. Check the DNS records for your custom domain’s hostname (e.g., auth.example.com).
  3. Ensure there is only one CNAME record with that name. If multiple CNAME records exist with the same name, delete all but one and keep only the Auth0-provided target value.
  4. Verify the CNAME target matches exactly what Auth0 provided (e.g., <tenant-id>.edge.tenants.us.auth0.com).

Step 2: Wait the full 48-hour window

  1. Note the exact time you added or last modified the CNAME record.
  2. Wait a full 48 hours from that time before attempting verification again. Auth0’s documentation explicitly states verification can take up to 48 hours.
  3. After 48 hours, return to Auth0 Dashboard → Branding → Custom Domains and click Verify again.

Step 3: Delete and re-create the custom domain (if still stuck after 48 hours)

  1. Navigate to Auth0 Dashboard → Branding → Custom Domains.
  2. Click the custom domain that is stuck in pending_verification.
  3. Click Delete and confirm the deletion.
  4. Wait 5 minutes for the deletion to propagate.
  5. Create a new custom domain with the same hostname.
  6. Copy the new CNAME target provided by Auth0.
  7. Update your DNS provider with the new CNAME record (or verify it matches if you are re-using the same target).
  8. Wait another 48 hours before attempting verification.

Step 4: Check for DNS provider-specific issues (if using Cloudflare)

If your domain is proxied through Cloudflare, the following may block verification:

  1. Cloudflare Zone Hold: Temporarily disable Zone Hold in your Cloudflare account (Cloudflare Dashboard → Domain → Settings → Zone Hold).
  2. Cloudflare Proxy Status: Ensure the CNAME record is set to DNS only (gray cloud icon), not proxied (orange cloud icon). Auth0 verification requires direct DNS resolution, not Cloudflare proxying.
  3. Retry verification after making these changes.

Step 5: Contact Auth0 Support (if still stuck after all steps)

If your CNAME record is correctly configured, resolves via external DNS tools, and verification remains stuck beyond 48 hours with no error message, this indicates a potential issue with Auth0’s verification service that requires account-specific investigation.

Contact Auth0 Support and provide:

  • Your tenant name
  • The custom domain hostname (e.g., auth.example.com)
  • The CNAME target value provided by Auth0
  • Proof that the CNAME resolves correctly (screenshot from a DNS checker tool like mxtoolbox.com or dns.google)
  • The exact date and time you added the CNAME record
  • How long the domain has been stuck in pending_verification

Auth0 Support can investigate Auth0-side logs to determine if there is a caching issue, polling delay, or tenant-level restriction preventing verification.

I would also recommend reviewing our documentation on Configuring a Custom domain using Auth0 managed certificate.

Kind Regards,
Nik