Validate hostname forwarding
Once Adobe has installed the certificate, you can use one of the following methods to validate that it is working.
Browser validation
You can use any browser to validate that a certificate is installed correctly. Type your CNAME with _check
as the path into the address bar. For example:
data.example.com/_check
If everything works, the browser shows SUCCESS
. If the certificate is not installed correctly, you are issued a security warning.
Command line (curl)
Most modern operating systems already have curl
installed.
Type the following into the command line:
curl data.example.com/_check
If everything works correctly, the console returns SUCCESS
.
-k
flag to disable the security warning to help with troubleshooting.Command line (nslookup)
Type the following into the command line:
nslookup data.example.com
If everything works correctly, Adobe’s data collection servers are returned:
Server: hiodsibxvip01.corp.adobe.com
Address: 10.50.112.247
Name: example.com.ssl.d1.sc.omtrdc.net
Addresses: 63.140.37.126
63.140.37.206
63.140.36.51
63.140.36.145
Aliases: smetrics.example.com
Update implementation code
Once you have validated that your certificate works correctly, you can update your Adobe implementation to use these values.
- For Adobe Analytics AppMeasurement implementations, update the
trackingServer
configuration variable. If you have an existing implementation, see Visitor migration for additional steps on how to prevent existing visitors from being counted as new visitors. - For Web SDK implementations, update the
edgeDomain
property within theconfigure
command.
Maintenance and renewals
Thirty days before your first-party certificate expires, Adobe validates whether the CNAME is still valid and in use. If so, Adobe assumes that you want to continue using the service, and automatically renews the certificate on your behalf.
Frequently asked questions
Is this process secure?
How can Adobe purchase a certificate for our domain?
Can I request that the certificate be revoked?
What encryption type is used?
Does this program incur any additional cost?
What cipher security levels does Adobe offer?
Adobe offers two cipher security levels to meet varying customer needs for security on first-party data collection. These levels determine which encryption algorithms are supported for HTTPS connections with Adobe servers. Adobe regularly reviews and updates the set of supported algorithms based on current security practices. If you would like to change your cipher security settings, contact Customer Care.
- Standard requires TLS 1.2 or newer and at least 128-bit encryption. It is designed to provide the widest device compatibility while maintaining secure encryption.
- High cipher security level requires TLS 1.2 or newer and removes support for weaker ciphers. It is designed for customers who desire the strongest encryption and are not concerned about support for older devices.
The following clients are known to be unable to connect with cipher security set to High:
- Windows 8.1 and earlier (last updated in 2018)
- Windows Phone 8.1 and earlier (last updated in 2016)
- OS X 10.10 and earlier (last updated in 2017)
- iOS 8.4 and earlier (last updated in 2015)
What HTTPS certificate types are supported?
Adobe supports both RSA and ECC certificate types to meet varying customer needs. RSA certificates are more widely supported for clients, but ECC certificates use less processing on both the server and client side. For Adobe-managed certificates, both RSA and ECC are provided. For customer-managed certificates, RSA is required and ECC is recommended. Modern clients support both RSA and ECC. The following clients typically only support RSA certificates:
- Windows Vista and earlier (last updated in 2012)
- Windows Phone 8.0 and earlier (last updated in 2014)
- OS X 10.8 and earlier (last updated in 2013)
- iOS 5.1 and earlier (last updated in 2012)
- Android 4.3 and earlier (last updated in 2013)