As part of a larger project that involves performance enhancements across the Curated platform, we’re changing the way we handle custom domains.

This change should only take a few minutes of your time, and once you’ve updated your DNS you won’t have to do this again in the future.

If you aren’t already using Cloudflare to manage your DNS and SSL, now would be the perfect time to sign up. It’s free, and having your publication website served securely will improve your SEO.

Hosting on a top-level domain

Step 1 - Remove the following A records, pointing to 109.107.35.239

  Name (or Alias) IP Address
@ (or blank) 109.107.35.239
www 109.107.35.239


Step 2 - Add the following CNAME records ​

Name (or Alias) Target
your-domain.com hosting.curated.co
www your-domain.com

Hosting on a subdomain

Step 1 - Remove the A record pointing to 109.107.35.239

Name (or Alias) IP Address
your-subdomain 109.107.35.239


Step 2 - Add the following CNAME record

Name (or Alias) Target
your-subdomain hosting.curated.co

If you are using a custom short link domain, then you will need to make changes similar to the “top-level domain” instructions as above.

Serving Your Website Over HTTPS

As mentioned at the beginning of this doc, it would be smart to start serving your Curated site over HTTPS since you already have to make a change to your DNS.

To do that, you’ll need to set up an account with CloudFlare. Once you have set up your CloudFlare account and have your DNS managed by Cloudflare, please let us know (we have to make an adjustment on our end so the site is served correctly).

We also recommend adding what CloudFlare refers to as a “Page Rule” to force all your publication site traffic through HTTPS. Read this CloudFlare support article to learn more.

To be clear, we do not support hosting SSL certificates from your registrar or web host. We can only serve your custom domain over HTTPS using CloudFlare at this time.