Skip to content
masterclassBuddyTech Buzz5 fresh blogs · 5:00 AM IST
Start learning

Kinde · Const

Custom domains

Kinde custom domains let a production environment use your own authentication URL instead of its Kinde subdomain. Add the domain in environment settings, publish Kinde’s CNAME records, then update the application’s issuer and redirect URLs.

How it works

A custom domain replaces the Kinde subdomain used for user-facing authentication. Configure it in the environment settings, add the generated CNAME records at your DNS provider, then update the application issuer and redirect URLs; Kinde verifies the DNS and provisions SSL before the domain is ready.

Returns

A verified, SSL-enabled custom authentication domain for the environment.

Key points

  • New environments start with a Kinde-provided subdomain, which the custom-domain setup can replace for production.
  • A typical configuration uses a dedicated authentication subdomain such as account.example.com.
  • Application configuration must match the custom domain exactly rather than merely using the same parent domain.
  • Start setup from the environment’s Custom domain page in the Kinde dashboard.
  • Publish the generated CNAME records at the domain provider to connect DNS to Kinde.
  • Successful verification changes the state to Provisioned and enables an SSL certificate.

Common mistakes

  • Use a subdomain such as account.example.com; the procedure does not support a bare root domain.
  • Keep the Kinde domain for Management API access and machine-to-machine applications.
  • DNS verification and provisioning are asynchronous, so the domain may not be available immediately.
  • For social sign-in, authorize the custom-domain callback URL in each identity-provider application.

Example: Use the custom domain as the issuer

const issuerUrl = "https://account.example.com";

const authUrl = `${issuerUrl}/oauth2/auth`;
console.log(authUrl);

Build authentication URLs from the configured custom-domain issuer instead of the Kinde subdomain.

When to use it

Present a branded sign-in URL instead of a Kinde subdomain.

Production authentication

Use the custom domain as the issuer and in callback and logout redirects.

Application configuration

Register custom-domain callbacks with external identity providers.

Social authentication

Interview questions

QHow is a custom domain configured?

Add the domain under Settings > Environment > Custom domain, enter a subdomain, and save it. Kinde then displays DNS details; create the requested CNAME records with the domain provider. After verification, the status becomes Provisioned and an SSL certificate is provisioned.

Follow-up: What application changes are required? Set the issuer URL, callback URLs, and logout redirect URLs to the exact custom domain, and update any relevant configuration files.

QWhat must change in an application after adding the domain?

The application must use the exact custom domain, including updating KINDE_ISSUER_URL. Callback and logout redirect URLs in Kinde must also be changed to the custom domain.

Follow-up: What should remain on the Kinde domain? Management API access and machine-to-machine applications continue to use the Kinde domain.

QWhat happens when the custom domain is provisioned?

The domain can be used for authentication endpoints after it is provisioned. Kinde also continues to expose auth endpoints through the original Kinde subdomain.

Follow-up: What is a social-login-specific requirement? Add the custom-domain callback URL to the social provider application so the custom domain appears on the sign-in form.

  • Kinde domain
  • Organization custom domain
  • KINDE_ISSUER_URL
  • CNAME DNS records
  • callback URL
  • logout redirect URL
  • Auth endpoints

Source: Use your own custom domain - Kinde docs. Checked 2026-10-15.