Skip to main content

Understand custom-domain certificate and deployment states

Understand each custom status-domain state and the next action required to move the domain to Active.

Custom-domain activation has separate certificate, edge deployment, and DNS routing stages. The status shown in the editor identifies the current stage; it is not the website monitor's Up or Down status.

Domain states

State Meaning What to do
Not configured No active custom-domain request exists Turn on Request custom domain, enter a hostname, and save
Pending certificate A managed certificate is being prepared or is waiting for its validation CNAME Add the Step 1 CNAME, wait for public DNS, and check again
Deploying The certificate is issued and the dedicated edge distribution is being created or updated Wait, then select Check / activate domain again
Pending DNS The edge distribution is deployed, but the custom hostname does not resolve to the displayed traffic target Add or correct the Step 2 CNAME, wait for propagation, and check again
Active The edge distribution is deployed and the custom hostname's CNAME matches the expected target Open the HTTPS custom URL and test it
Error Activation could not continue because of a configuration or managed-service error Review the message, correct the cause, and retry or contact support
Disabled The hostname is saved but custom-domain service is turned off Enable and complete activation again if it should return

How a state advances

Check / activate domain performs the current-stage check. Activation does not continuously poll DNS or the edge network in the background. After adding DNS or waiting for an external deployment, select the button again to refresh the state.

The normal sequence is:

  1. Pending certificate
  2. Deploying
  3. Pending DNS
  4. Active

A state can remain unchanged while DNS caches expire, the certificate authority checks the validation record, or the edge network deploys the dedicated distribution.

Certificate validation and routing are different

The Step 1 CNAME proves control of the custom hostname to the certificate authority. The Step 2 CNAME sends visitor traffic to the status-page distribution. Both records are required, and their names and values are different.

Do not replace the validation record with the routing record. Keep the validation CNAME after the domain reaches Active so certificate renewal can continue.

What Active confirms

Active confirms that:

  • The managed certificate is issued.
  • The dedicated distribution reports Deployed.
  • Public CNAME resolution matches the generated traffic target.

It does not mean the monitored website is Up. The public page separately displays the monitor's current availability state.

Related articles

Did this answer your question?

Your response helps improve this Help Center.