Only subdomains can be used to serve your documentation. Apex domains cannot be used.
See the table below:
Custom domain type
In short, CNAME your subdomain to
Given the number of existing managed DNS providers, we cannot provide an actual setup process for all of them. Usually, you simply have to enter the actual subdomain part, without the root domain, and choose a CNAME type with
hosting.gitbook.io as its value or target.
For example, if your root domain is
mycompany.com, here is the proper configuration on Cloudflare if you wanted your documentation to be served at
In order for DigiCert to issue an SSL certificate for your custom domain, it must be allowed to do so. CAA records allow you to specify who can issue an SSL certificate for the custom domains that you own.
When no CAA record is registered for a domain, it means that anyone can issue an SSL certificate for it. If this is your case, your domain is already properly configured to be used with GitBook.
If you already have a CAA record for your custom domain, you must explicitly allow DigiCert to issue an SSL certificate for it by adding the following record:
0 issue "digicert.com"
If you domain is hosted on Cloudflare, you may be tempted to activate Cloudflare's proxying (the orange cloud, also called "Proxy status" in your domain settings).
While this configuration might work on most cases, we heavily discourage activating it. First, because your custom domain will already benefit from Cloudflare's CDN and a DigiCert SSL certificate. But this option also obfuscates the DNS target for your domain to the public, preventing GitBook to properly run routine checks on your custom domain.
Whenever possible, turn off Cloudflare proxying to ensure that your documentation is served without issues and can be monitored by GitBook.