Custom domains are available for any site on a paid plan.

Before you start adding a custom domain, there are a few key things to note:

Shifter uses CNAMES for custom domains. This works like a "mask" of the Shifter domain created with each site.

For example, example-site.on.getshifter.io is masked with example-site.com.

If you want to assign a non-www domain such as example.com, your DNS provider must support ALIAS  Records.
Non-www domains are commonly referred to as naked or apex domains. If you are not sure if your DNS provider supports them, contact your provider or check their documentation.
The following DNS providers support ALIAS /ANAME  records

Before we can add a custom domain name, we must first verify the ownership of the domain to assign the domain and enable HTTPs for your site. It will help ensure that all site traffic is secure. HTTPs is required for all Shifter sites and is enabled by default.

Once your domain is verified and ready, add a CNAME record like shown below to enable that custom domain.

Before jumping into the specifics, here's a brief overview of how-to enable a custom domain on Shifter.
Shifter uses only CANAME (or ANAME/ALIAS). If you have a mail server (MX), do not delete or overwrite the current records.
​  

https://go.getshifter.io/ 

This sample set's main domain is example.com, and the alternative is www.example.com.
Enter your domain name into the [Enter your domain] form.

If you need a www prefix, check "Include the alternative domain (www.YOUR-DOMAIN-NAME)"

For more details for adding DNS records, checkout other documents: DNS Providers Guides.

In this example, we are using Amazon's Route53 DNS service. Depending on your provider, this screen may look different. However, the steps are the same.

Note 1:  Do not delete verification records
Once you have added verification records and verified them, do not delete them. We'll check them to automatically extend your domain name's SSL/HTTPS expiration date. SSL/HTTPS will expire and will no longer be updated if you delete verification records.

Note 2: Trim the last dot of the value
In the above sample, the published record is _42a5e0a2171b9111b23bb44420a7215e.ltfvzjuylp.acm-validations.aws. , but some DNS providers don't accept tailing dot records. So, you have to trim it when you add them.
For example: _42a5e0a2171b9111b23bb44420a7215e.ltfvzjuylp.acm-validations.aws
​

www prefixed domain (www.example.com)

Naked domain (example.com)

Note 2.   Prohibited underscore-started DNS record.

DNS servers or providers should accept the DNS records that start with _   (underscore/underbar) for verifying domains. Please ask your DNS provider if they support underscore DNS records. Here are some DNS providers that support underscore records: Route 53, GoDaddy, NameCheap, Name.com and MuuMuu Domain.

You can strip the initial underscore from the DNS records if your DNS provider doesn't support underscore-started records. For more details, read the AWS support document: Underscores Prohibited by DNS Provider

Here's a sample: 

www prefixed domain (www.example.com)

naked domain (example.com)

Note: If you fail to validate your domain, make sure the added records in your DNS provider does not contain your domain name.
For example, if you input _abc123.www.your-domain.com , it should be _abc123.www .

For more details for adding DNS records, check out other documents: DNS Providers Guides.

** "CloudFront Domain" is available on "Site Settings" page of your Shifter dashboard

Please note: After attaching a custom domain to an artifact, generate it again to replace Shifter's URLs  (e.g. abcd-1234.on.getshifter.io) to your custom domain for your contents.
​

Back to [Overview] and make sure custom domain name is applied.

That's all!