Custom Domains

Auth0 allows you to map the domain for your tenant to a custom domain of your choosing. This allows you to maintain a consistent experience for your users by keeping them on your domain instead of redirecting or using Auth0's domain. For example, if your Auth0 domain is, you can have your users to see, use, and remain on

Using custom domains with centralized login is the most seamless and secure experience for developers and end users. For more information, please see our docs on centralized login and customizing the hosted login pages.

Custom Domains is a beta feature available only for paying public-cloud tenants with their environment tag set as Development.


You'll need to register and own the domain name to which you're mapping your Auth0 domain.

Features Supporting Use of Custom Domains

Currently, the following Auth0 features and flows support the use of custom domains:

  • OAuth 2.0/OIDC-Compliant Flows (those using the /authorize and /oauth/token endpoints)
  • Guardian (Version 1.3.3 or later)
  • Emails (the links included in the emails will use your custom domain)
  • Database and Social connections

Token Issuance

Auth0 issues tokens with the iss claim of whichever domain you used with the request. For example, if you used to obtain an access token, the iss claim of the token you receive will be If you used your custom domain, the iss claim value will be

If you obtain an access token for the Management API using an authorization flow with your custom domain, you must call the Management API using the custom domain (your token will be considered invalid otherwise).

Certificate Management

Auth0 offers two certificate management options.

  • Auth0-Managed Certificates: Auth0-managed certificates are those where Auth0 will manage the creation and renewal of the certificates for your custom domain. This is the simplest custom domains deployment option, and the scope of this document

  • Self-Managed Certificates: Self-managed certificates are available for enterprise customers only. Choosing this option means that you are responsible for managing your SSL/TLS certificates and configuring a reverse proxy to handle SSL termination and forwarding requests to Auth0.

How to Configure Custom Domains

Setting up your custom domain using Auth0-managed certificates requires you to do the following steps:

  1. Provide your domain name to Auth0
  2. Verify ownership
  3. Complete feature-specific setup

Step 1: Provide Your Domain Name to Auth0

Log in to the Dashboard and go to Tenant Settings. Click over to the Custom Domains tab.

Enter your custom domain in the provided box and select Auth0-managed certificates. Click Add Domain.

Step 2: Verify Ownership

Before you can use this domain, you'll need to verify that you own your domain. To do this, you need to add the CNAME verification record listed in the Dashboard to your domain's DNS record.

When you've done so, click Verify to proceed.

It may take a few minutes before Auth0 is able to verify your CNAME record, depending on your DNS settings.


Here's how to add the CNAME verification record to your domain's DNS record. The steps specified may vary by domain host provider, but generally speaking, you will need to:

  1. Log in to your domain management service (such as GoDaddy or Google Domains)

  2. Create a new record:

    • For the record type, indicate CNAME
    • For the Name field, enter your custom domain name (such as
    • Leave the Time to Live (TTL) field set to the default value
    • In the Value field, paste in the CNAME value provided by the Auth0 Dashboard

When done, save your record.

If Auth0 was able to verify your domain name, you'll see a confirmation window.

This means the verification process is complete and within 1 to 2 minutes, your custom domain should be ready to use.

If you are unable to complete the verification process within three days, you'll need to start over.

Step 3: Complete Feature-Specific Setup

There are additional steps you must complete depending on which Auth0 features you are using.

If you have been using Auth0 for some time and decide to enable a custom domain, you will have to migrate your existing apps and update the settings as described below. Note that existing sessions created at will no longer be valid once you start using your custom domain, so users will have to login again.

Configure the Hosted Login Page

If you're using the default Hosted Login Page without customization, you will not need to make any changes. Your custom domain will work right out of the box.

If you're using a custom Hosted Login Page, you'll need to update it to use your custom domain. The changes that you'll need to make are regarding the initializing of Lock. The following code sample shows the lines reflecting the necessary changes.

var lock = new Auth0Lock(config.clientID, config.auth0Domain, {
	configurationBaseUrl: config.clientConfigurationBaseUrl,
	overrides: {
		__tenant: config.auth0Tenant,
		__token_issuer: config.auth0Domain

Embedded Lock

If you're using Embedded Lock (Lock v11), you need to use your custom domain when initializing Lock. You will also need to set the configurationBaseUrl to the appropriate CDN URL:

var lock = new Auth0Lock('your-client-id', '', {
    configurationBaseUrl: ''

The CDN URL varies by region. For regions outside of the US, use https://cdn.{region}


If you are using Auth0.js or other SDKs, you will have to initialize the SDK using your custom domain. For example, if you are using the auth0.js SDK, you'll need to set the following:

webAuth = new auth0.WebAuth({
  domain:       '',
  clientID:     'your-client-id'

Auth0 Emails

If you would like your custom domain used with your Auth0 emails, you'll need to enable this feature in the Dashboard. You can do this by clicking the toggle associated with the Use Custom Domain in Emails. When the toggle is green, this feature is enabled.

Social Identity Provider Configuration

If you want to use social identity providers with your custom domain, you must update the allowed callback URLs to include your custom domain (such as

You cannot use Auth0 developer keys with custom domains.


If you are using Auth0 with a custom domain to issue access tokens for your APIs, then you must validate the JWT issuer(s) against your custom domains. For example, if using the express-jwt middleware:

	issuer: '', 
	... additional params ...

If you are using built-in Auth0 APIs, such as the Management API, the API identifier will use your default tenant domain name (such as and


  1. If I use a custom domain, will I still be able to use my domain to access Auth0?

Once you enable your custom domain in Auth0, you should be able to use either the default or your custom domain. There are a few exceptions:

  • If you are using embedded lock or an SDK, the configuration is pre-defined as using either your custom domain or the domain, so you have to use one or the other.
  • If you start a session in, and go to, the user will have to login again.
  1. What about support for other features?

We are planning to support several additional features in the future, including SAML and WS-Fed clients and enterprise and Passwordless connections.

Was this article helpful?