Use your own domain
A default URL is assigned to your privacy center, for example:
We recommend using your own domain name instead, such as
We offer two options to setup that custom domain:
Read on to learn how to do that setup.

Managed by Didomi

In this setup, your custom domain will be managed by Didomi and you will simply need to create a DNS record.

Step 1 - Create the DNS record for your custom domain

Create a DNS record with your DNS provider or registrar that manages your domain, and use the following configuration parameters:
Parameter name
Your custom domain ( or similar)
You will be creating a DNS record for a specific sub-domain of your domain name (like privacy., for instance) and not delegating the DNS management of your whole domain.
NS (Name server)
The type NS allows us to generate SSL certificates for the sub-domain and serve your privacy center with SSL/HTTPS.
TTL (seconds)
Didomi's name servers that will host the DNS records for your custom domain
If you need help with this step, feel free to reach out to [email protected] and we'll be happy to help.
If you are using CloudFront from Amazon Web Services
To support your custom domain, we will create a dedicated CloudFront distribution with your custom domain as a CNAME. Because of AWS restrictions, it is not possible for us to create that distribution if you already have a distribution in your account with either the exact same CNAME or a matching wildcard CNAME. For instance, if you have chosen to use the custom domain and already have a CloudFront distribution with either or * as CNAMEs, we will not be able to create the custom domain for you and the step 2 above does not apply.
If you are in this situation, please read the instructions below and contact us if you need help.

Step 2 - Declare the custom domain

Before we can start serving your privacy center on your custom domain, we need to setup our DNS servers to recognize it.
Send an email to [email protected] or to the person you have been in touch with at Didomi to let us know what custom domain you will be using and that the setup is done on your side.

Managed by AWS CloudFront

If Didomi cannot manage your custom domain (which happens in rare cases when you already use AWS CloudFront on your own) or if you want to setup your custom domain yourself on AWS CloudFront, follow these instructions.
In this configuration, you will need to create your own CloudFront distribution with a SSL certificate and a DNS record that points to that distribution.

Create a CloudFront distribution

Create a CloudFront distribution with a Web delivery method and apply the following configuration parameters:
Configuration parameter
Origin Domain Name
This is Didomi's upstream/origin servers that CloudFront will query to serve the content of your privacy center on your custom domain.
Viewer Protocol Policy
Redirect HTTP to HTTPS
Allowed HTTP Methods
Cache Based on Selected Request Headers
Whitelist > Add the following headers from the list: Accept, Accept-Charset, Accept-Datetime, Accept-Language, Authorization, Host, Referer
Minimum TTL
Maximum TTL
Default TTL
Forward Cookies
Query String Forwarding and Caching
Forward all, cache based on all
Compress Objects Automatically
Alternate Domain Names (CNAMEs)
Your custom domain name
This is where you specify the custom domain name that you have chosen. It allows CloudFront to know that your custom domain is served by this distribution. See the AWS documentation for more information.
Custom SSL certificate
Choose the SSL certificate that matches your custom domain name or a wildcard
If you do not have a SSL certificate for your custom domain, you can create one in AWS Certificate Manager.
Use the default value for all the other configuration parameters of the CloudFront distribution.

Create a DNS record

Now that your CloudFront distribution has been created, you need to create a DNS record that points to it.
Create a DNS record for your custom domain name and configure it as a CNAME of the CloudFront distribution. See the AWS documentation for more information on how to create that record on Route53 or another DNS provider.
Last modified 3yr ago