Test your property settings and then go live with your website on the Akamai edge network.
You need the unique alphanumeric value assigned to your contract and primary group, prefaced by their PAPI prefixes —
You also need the unique
propertyId prefaced with its PAPI prefix—
Finally, you need the edge hostnames you created and added to your property.
While it's not required, you should thoroughly test your website or app.
To start, activate your property on the staging network.
In your activation, set
"fastPush": true to enable Fast activation feature. The
notifyEmails addresses you set will get a message when the property is active on staging.
Temporarily set up your local browser to target an edge server to access your property.
You need your edge hostname's actual IP address. You can get it by appending
-stagingto your stored edge hostname, and running a command from a Terminal or Command Prompt. For example, assume the domain you set in your edge hostname was "example.com" and you're using a Standard TLS certificate that adds the edgesuite.net suffix to your hostname behind the scenes. The appended hostname might look like this:
Open a new terminal, and perform a
digof your edge hostname:
IPv4 + IPv6 dual stack
dig AAAA www.example.com.edgesuite-staging.net
Open a new command prompt, and perform an
nslookupof your edge hostname.
IPv4-only / IPv4 + IPv6 dual stack
Open your local hosts file in a text editor. Based on your operating system, you may be able to find your host file as follows:
|Linux/macOS||Navigate to |
|Windows||Navigate to |
The above paths are only examples of where this file might be found. Please see the relevant user documentation for the location of the Hosts file for your selected operating system.
At the end of the hosts file, add an entry for the actual domain to your website that includes the edge hostname's IP address.
Save and close your hosts file. All requests from your local system to your domain will now go to an edge server.
- This applies to your local system, only.
- To undo the redirection to the edge server, remove the new entry from your hosts file.
When a browser requests your content on staging edge servers, Akamai adds the
X-Akamai-Staging HTTP response header to the request. Look for this header in a request to make sure your browser is pointed to the staging network.
Close all browser windows, reopen your browser, and clear the browser cache.
Access the Network functionality in your browser:
- Chrome. Right-click in the browser window and select Inspect. Click the Network tab.
- Edge. Press F12, and then press Ctrl+4 to open the Network utility.
- Firefox. Press Ctrl+Shift+I (Windows) or Command+Opt+E (macOS). This takes you to the Network tool.
- Safari. If necessary, select Safari > Preferences, click Advanced, then enable Show Develop menu in menu bar. Select Developer > Show Web Inspector and select the Network tab.
Point your browser to the domain you included in your local hosts file.
In the Network section, click the first file listed.
Review the response headers. If you see
X-Akamai-Staging: EdgeSuite, you're good. If not, go back to 2 - Point your browser to edge servers and make sure you followed the process correctly.
Check for the
HTTP/1.1 200 OK Server: Apache/2.4.9 (Unix) OpenSSL/1.0.1-fips Last-Modified:Wed, 26 Jun 2022 18:28:37 GMT ETag: "1234-5a678b9012c34" Accept-Ranges: bytes Content-Length: 13162 Content-Type: image/gif Cache-Control: max-age=603241 Expires: Mon, 14 Apr 2022 16:48:38 GMT Date: Mon, 07 Apr 2022 17:04:37 GMT X-Akamai-Staging: EdgeSuite X-Cache: TCP_MEM_HIT from b128-48-122- 38.deploy.akamaitechnologies.com (AkamaiGHost/184.108.40.206-12528292) (-) X-Cache-Key: /L/12345/678910/1a/orign-example.com/images/samplepicture.gif?234567 Connection: keep-alive
Use this table to interpret the results.
|Did the page load as expected?||Is the X-Cache entry present?||Result|
Success! You're ready to test.
You reached an edge server, but something isn't working. The value of the
You reached your origin server, not an edge server. Check the entry you added to your hosts file.
You haven't reached your origin server or an edge server. Check the entry you added to your hosts file.
Access your website the same way you normally would to test it.
When testing, use your actual domain for requests—don't use its edge hostname. Edge hostnames are only used by your DNS to reroute requests to the Akamai edge network.
Check key functionality.
Once you're satisfied that your property works, remove the hosts file entry you added and then save it.
On macOS 10.6 and later, flush your DNS cache again with the
Begin delivering your website or app to your end users through the Akamai edge network.
Push your property to the production network.
In your activation,set
"fastPush": true to enable Fast activation feature. The
notifyEmails addresses you set will get a message when the property is live on the production network.
To go live and deliver your content to end users, you need to modify your origin DNS settings outside of Property Manager. Replace your existing CNAME record and with a new one, setting its value to the edge hostname you assigned to your property.
Make note of the existing DNS entries for use in troubleshooting.
Here's an example of a generic DNS record for a domain, before you move it to the Akamai edge network. In it,
220.127.116.11 represents the IP address for your origin server:
example.com. IN A 18.104.22.168
Here's an example of that same domain in a DNS record, pointing to Akamai's Standard TLS network:
example.com. IN CNAME example.com.edgesuite.net
If you notice a problem after switching your content to the production network:
Roll back the DNS change to point your website or application back to your origin server.
Report the problem to Akamai.
This helps you and Akamai identify the problem in a controlled environment without affecting live end users.