Find answers to frequently asked questions about the DOM application.

General questions

Is domain validation mandatory?

Domain validation is currently optional. DOM checks will not be enforced, and you will not be blocked from activating a configuration version with a new hostname. This is to allow for familiarization with the new process. DOM will be enforced, with mandatory domain validation as a prerequisite for all new onboarded hostnames, in a later phase. New customers will be automatically enrolled in the enforced mode, and existing customers will gradually be transitioned to enforced mode.

Do I need to validate existing/active hostnames?

No, you don’t. Existing hostnames that are currently active in a Property Manager configuration are considered validated. Hostnames are validated at the HOST level. Wildcards are validated at the DOMAIN level. The new validation process only applies to newly added domains or if one of those existing hostnames is moved to a different property.

Is the validation done from IP/server in an ACL?

The validation is done from edge servers, part of the Origin IP ACL list.

Access and permissions

Why can’t I see some action buttons in the DOM application?

Access to the DOM UI is controlled by permissions. If you have read-only access, you can see a list of domains and monitor their status, but you don’t see the action buttons. If you have write permissions, you can submit a domain for validation. If you have delete permissions, you can invalidate and delete domains. The permissions are:

• domainValidationRead. Grants read-only access to the DOM UI. Users with this permission can view submitted domains and their validation status, but cannot make changes.
• domainValidationWrite. Grants write access to the UI. Required to submit new domains for validation and to validate domain validation via DNS or HTTP methods.
• domainValidationDelete. Grants the ability to invalidate or delete a domain from the system. Used when a domain is no longer needed or ownership has changed.
  A record can only be deleted

Validation process and scope

What are the different levels of validations?

You can validate a HOST (exact domain), WILDCARD (one level of subdomains) and DOMAIN (entire domain, that is all levels of subdomains). Read more.

How can I monitor the validation status?

The DOM application lists all the domains submitted for validation with their current status. To view details about the domain, its validation, and the status history, click the Action menu icon and click View Details.

Why is a status stuck in the Validating state?

See Domain status stuck in the Validation in Progress state for more details.

What is the order/precedence of the validation methods?

When a new hostname is detected and added for validation, all 3 methods are checked. Whichever method gets a positive result will mark the hostname as validated. There is no order or precedence per se, as all 3 methods are done independently of one another.

Do the validation tokens expire?

Yes, you need to complete the validation process in that timeframe. View the domain details to check the expiration date. If your token has expired, resubmit your domain for validation to get a new token.

Does a completed validation expire?

Once completed, a validation does not need to be repeated or renewed. It is valid until it is invalidated.

I am using a custom certificate in Certificate Provisioning System. Can DOM process the validation through CPS?

The validation through the CPS system is performed by a third-party, independent Certificate Authority, which ​Akamai​ has no visibility into. ​Akamai​ can't confirm domain ownership for a custom certificate via CPS.

Common Scenarios

Can I validate a hostname (sub-domain) if another account has already validated the top-level?

Yes, both accounts would go through the validation process for each of the hostnames separately.

Can a hostname be validated on two accounts at the same time, for example, if getting ready for transferring the hostname?

Yes, multiple accounts can have a validation record for the same domain, but only one account is allowed to add or activate it in a configuration.

Do I have to repeat the validation if I move a hostname from one configuration to another within the same account?

No, you don’t need to repeat the validation. DOM has an account-level scope.

What happens when a full configuration is moved to another account?

You don’t need to repeat domain validation as the hostname is already active.

What happens if we need to move hostnames to another account, without moving the whole configuration?

Transferring a hostname between accounts (i.e.: inter-account hostname move) has not changed. You need to perform validation on every step where you add a hostname. Read more about migrating hostname between accounts .

If a hostname active in one account is added to another account, what will happen?

This situation is not allowed and you’ll see an error.