There are three methods you can use to complete the domain validation: DNS CNAME, DNS TXT, and HTTP.

DNS CNAME

In this method, ​Akamai​ generates a CNAME record that you copy to your DNS to automatically handle domain validation challenges and certificate renewal. You can use the same CNAME value to validate a default certificate and to prove domain ownership to ​Akamai​. The DNS CNAME method is recommended in most cases.

Use this method when:

• You have direct control over your DNS records.
• You want to validate an exact host, a wildcard, or a top-level domain.
• You are using a default certificate, which lets you use a DNS CNAME record for both the certificate and domain validation.

Don't use this method when:

• You don’t have control over your DNS records.
• You are using multiple CDNs.
• You are not using a default certificate.

How to:

1. Submit your domain for validation.
2. View the domain details.
3. Copy the DNS CNAME value from the Validation Details section.
4. In your DNS configuration:
   • Add a CNAME record: _acme-challenge.domainName. For a domain called example.com, the record should be _acme-challenge.example.com.
   • Paste the DNS CNAME you copied from the DOM UI as the target.

DNS TXT

In this method, ​​Akamai​ provides a challenge token that you use to set up a TXT record in your DNS configuration.

Use this method when:

• You have direct control over your DNS records.
• You want to validate an exact host, a wildcard, or a top-level domain.
• You are using multiple CDNs and want to manage domain validation through multiple TXT records in your DNS.

Don't use this method when:

• You don’t have control over your DNS records.
• You don’t want to manually obtain a TXT token and add it to your DNS records for domain validation.

How to:

1. Submit your domain for validation.
2. View the domain details.
3. Copy the challenge token from the Validation Details section.
4. In your DNS configuration:
   • Add a TXT record: _akamai-{host|wildcard|domain}-challenge.domainName.
     Include the host, wildcard or domain part, depending on the validation scope of your domain. For a domain called example.com and the DOMAIN validation scope, the record should be: _akamai-domain-challenge.example.com.
   • Add the challenge token you copied from the DOM UI. The format can be either “token=1234….5678” or “1234….5678”.

HTTP

In this method, you create a file containing a token and save it on your origin server at the provided URL. This method is available for hosts (single hostnames).

Use this method when:

• You don’t have access to a DNS zone.
• You’re using multiple CDNs. In this Multi-CDN scenario, you need to manage domain validation through files on the origin server.

Don’t use this method when:

• You want to validate a domain with a WILDCARD or DOMAIN validation scope.
• You don’t want to manually obtain the new challenge tokens from ​Akamai​ and add them to a file on your origin server.

How to:

1. Submit your domain for validation.
2. View the domain details.
3. Copy the challenge token from the Validation Details section.
4. Create a file and paste the challenge token as the file contents:

   cd <web-server-www-root>
   mkdirs /.well-known/akamai/akamai-challenge
   echo -n "your-verification-token" > /web-server/.well-known/akamai/akamai-challenge/<challenge-path-token>
   

• Place the file on your HTTP server, in the location given as the HTTP Redirect From URL in the DOM UI. The last part of the URL must be the file name.
• Alternatively, you can use a redirect to the HTTP Redirect To URL with the challenge token.