Custom Domains for News Center

When you turn on your News Center, your content is available through by default. Your URL will look like this:

If you’d like to use a different URL, you can create one by setting up a custom domain. You can do so by:

1. Entering your custom domain
2. Creating a custom CNAME record
3. Choosing to configure SSL

To recognize logged-in Users on your News Center, your web app (where you have Intercom installed) and your News Center must share a top level domain. E.g. If your domain is, your custom News Center domain must be something like This allows Intercom to identify your logged-in users when they visit your News Center.

Enter your custom domain

Enter the custom domain you want to use in your News Center settings. Let’s use ‘’ as an example:

Create a custom CNAME record

  • Go to your DNS provider’s website (e.g. GoDaddy or Cloudflare). If you’re choosing one for the first time, go with one that supports SSL.
  • Create a CNAME (‘canonical name’) record for your custom domain.
  • Point it at Intercom’s host domain
Region support

We currently don't support custom domains for News in Australia or Europe.

How to create a custom CNAME record with Cloudflare

These steps will vary, so check with your own DNS provider for support.
As an example, here’s how to set up a CNAME record with Cloudflare:

  1. Set up Cloudflare as the resolver for your custom CNAME by changing your domain nameserver to Cloudflare.
  2. Go to the ‘DNS’ section in Cloudflare and add a CNAME record for your News Center custom domain. Give the CNAME a Name based on the first part of your custom domain e.g. if your custom domain is, use news-center.
  3. Point it at the Intercom host domain:

To enable the CNAME record, toggle on Proxy Status so that cloud icon is orange.

Choose to configure SSL (optional)

After you set up a custom domain, your News Center will be hosted on your domain, but on HTTP rather than HTTPS. Your News Center will now appear as ‘not secure’ on web browsers like Chrome Here’s how to secure it.

SSL (or TLS), is the most widely used way to secure the connection between your server and your browser. It ensures the connection between the server and browser is encrypted and safe, and appears as HTTPS.

Here’s what an SSL-configured website (with HTTPS) typically looks like on the Chrome browser:

This is what it looks like if you’ve visited a website not secured by SSL (without HTTPS):

There are two ways to set up SSL with the News Center on your custom domain:

  • Use a flexible SSL (using a third party DNS provider like CloudFlare or AWS CloudFront)
  • Use your own SSL certificate (using a TLS Termination Proxy)

You can configure SSL for your custom domain to keep sensitive information encrypted. If you want to do this, make sure you’ve set up your CNAME with a DNS provider that supports SSL, like Cloudflare.

DNS Changes can take time

DNS changes can sometimes take up to 72 hours to take effect, but are typically much faster.

How to configure SSL with Cloudflare

Add SSL support to your domain

Go to the SSL/TLS section and change SSL to ‘Flexible’ or ‘Full’.

A screenshot from the section of the CloudFlare user interface which allows you to toggle between encryption modes

Don’t choose ‘Full (Strict)’ as this will result in an invalid SSL certificate.

Create a page rule enforcing HTTPS

Go to ‘Page Rules’ and create a new page rule with the following settings, replacing with your own custom domain.

Disable Cloudflare page speed features

Go to ‘Speed’ and disable Rocket Loader and Mirage for your custom News Center domain.

Both of these features result in Cloudflare attempting to add some javascript to your News Center. This will break functionality on your News Center due to security settings your News Center has enabled.

Ready to go!

Your custom domain should be fully secured and ready to go. Visitors to your News Center will see the green lock icon in their browser to let them know the site is secure.

How to configure SSL with AWS

Create a CloudFront Distribution

  1. Sign in to the AWS Management Console and open the CloudFront console.
  2. Choose Create Distribution
  3. Update the 'Origin' settings. The origin domain will be and the protocol should be HTTPS only. Our servers support TLSv1.2.
  4. Update the 'Default cache behavior' settings.

❗️ Cookie Forwarding and Query String Forwarding

It is important that your Cloudfront distribution's behaviour is set up to forward all Headers, Cookies and Query Strings or else features of the News Center may not work

🚧 Cache Settings Changed

When setting up your Cloudfront distribution, you need to select "Use legacy cache settings", which will now show the options for:

  • Headers
  • Query strings
  • Cookies

These should be set to All

  1. Under 'Settings', add your custom domain, e.g. as an Alternate domain name and upload your SSL certificate if you have one. You need a certificate that matches your domain. If you use a certificate that does not match your domain, then you will see the following error when navigating to the HTTPS version of your website: NET::ERR_CERT_COMMON_NAME_INVALID

Create a CNAME record

  1. Copy your distribution domain name
  2. Navigate to your domain provider and create a new CNAME record
  3. For host/name input your subdomain (ex news)
  4. For value input your CloudFront distribution domain name

Using your own SSL certificate with Apache or Nginx

The SSL certificate used by your News Center is a shared certificate signed by your DNS provider. It uses SNI (Server Name Indication) to secure your site.

If you wish to host your own security certificates, you can do so through a TLS termination proxy. You’ll need to edit the configuration file on your proxy webserver.

Note: If you created a CNAME record that points to, you'll need to delete this to host your own SSL certificate.

Here are the basic instructions to set up your own SSL using Apache and Nginx webservers:

# Prerequisites: mod_ssl, mod_proxy and mod_proxy_http should be enabled

# Step 1: Acquire an SSL certificate and private key (e.g.
# Step 2: Set up Apache proxy settings, example below.
# Step 3: Set custom domain in Intercom News Center settings
# Step 4: Make sure your custom domain's DNS record resolves to your Apache server

<IfModule mod_ssl.c>
<VirtualHost *:443>
        ServerName # specify your custom domain here

        # Set SSL options for your own domain
        SSLEngine on
        SSLCertificateFile /path/to/your/fullchain.pem
       	SSLCertificateKeyFile /path/to/your/privatekey.pem
        # Proxy SSL options
        SSLProxyEngine on
        SSLProxyVerifyDepth 10
        SSLProxyCheckPeerCN off
        SSLProxyCheckPeerName on

       # Set up the reverse proxy to Intercom
        ProxyPreserveHost On
        ProxyPass /
        ProxyPassReverse /
# Prerequisites: ngx_http_ssl_module and ngx_http_proxy_module should be enabled

# Step 1: set up normal server with HTTPS
# Step 2: set up proxy settings as shown below 
# Step 3: set custom domain in Intercom News Center settings
# Step 4: make sure your DNS record is configured to IP of your Nginx server

resolver; # use own DNS server if you have one
server {
  listen 443 ssl;
  server_name; # replace this with your domain

  ssl_certificate /path/to/your/fullchain.pem;
  ssl_certificate_key /path/to/your/privatekey.pem;

  location / {
    # using "set" is important as IP addresses of Intercom servers 
    # changes dynamically. "set" enables nginx to follow dynamic IPs
    set $intercom ""; 
    proxy_set_header Host $host;
    proxy_pass $intercom;

There are many ways to set up your own SSL certificate - we can’t guarantee that we can support every type of proxy setup. If you have specific needs, we can't support you in configuring it.

Note that you may also need to add redirect from HTTP protocol (port 80) to HTTPS as part of your server configuration.

While most modern browsers support SNI, a few older ones don’t. If you’re supporting those browsers, you should use your own SSL certificate instead. Check with your DNS provider to see if this option is available.