Skip to content

How to Use a Custom Namecheap Domain with GitHub Pages?

This post will guide you through the different steps needed to configure a custom Namecheap domain with your static website hosted on GitHub Pages.

ZEIT Tolino Cover Picture


This guide focuses on Namecheap as a domain name provider. The overall approach is likely similar to other domain name providers, however, the steps outlined below are specific to Namecheap and cannot be applied to other domain name providers directly.


Sometimes you want your GitHub Page to be reachable via a custom domain to provide a catchy name or to put it next to your existing website by using a subdomain. Note, that there are a bunch of resources on this topic out there already, but it seemed like none of them puts all the required pieces into a single place, thus I came up with this guide.


Consider the following example: The GitHub repo of this blog is located at and the default domain for its corresponding GitHub Page would be Now as you can see, I obtained the domain from Namecheap and used the subdomain as the custom domain for this blog.


Let's configure a custom domain for your GitHub Page.


This guide assumes the following prerequisites to be fulfilled:

  1. You have a GitHub repository set up and its corresponding static GitHub Page is published at the default domain name (i.e. <user><repo>)
  2. You bought a domain on Namecheap and can configure it via the Namecheap Dashboard

Namecheap Configuration

Head over to your Namecheap Dashboard and hit the MANAGE button:

Namecheap Dashboard

On the Domains → Details page click the Advanced DNS tab:

Namecheap Dashboard

In the Host Records section, you need to add five entries. Four of them are of type A Record with Host being @ pointing to the GitHub Pages IP addresses. The fifth record will be the actual CNAME Record pointing to your default GitHub Page domain. The below screenshot shows the values needed to map your new custom domain ( in this case) to the default GitHub Pages domain ( as given in the above example.

Namecheap Dashboard

Copy the values from this table and configure your host records accordingly.

Type Host Value TTL
A Record @ Automatic
A Record @ Automatic
A Record @ Automatic
A Record @ Automatic
CNAME Record blog Automatic


Both subdomains and apex domains are supported with GitHub Pages. If you prefer to use the apex domain instead of the subdomain you have to enter www instead of blog in the Host column since www is just a usual subdomain from DNS perspective.

It usually takes a while until this configuration becomes active. After waiting for one hour verify your DNS settings to be active by running the following command (replace with your domain of course):

dig +noall +answer +nocmd
Your output should look similar to this one:  1799    IN  CNAME 3600    IN  A 3600    IN  A 3600    IN  A 3600    IN  A

If you get the expected output, your Namecheap configuration is in place and we can proceed with the configuration of GitHub.

GitHub Pages Configuration

Go to your GitHub repository and navigate to the GitHub Pages settings. For this blog the URL is Given the above-mentioned prerequisites, your static website should already be deployed to GitHub Pages and accessible via the default URL (if you still need to set up the deployment, I'd suggest having a look at the GitHub Actions Workflow of this blog, check out the GitHub docs on publishing your website or reading the docs of mkdocs-material regarding publishing).

Scroll down to the Custom Domain section and enter your custom domain into the input field. In the case of this blog was entered:

GitHub Pages Custom Domain Settings


Again, if you prefer to use your apex domain, simply omit the subdomain and enter e.g. here.

In case your Namecheap configuration was successful as described above, the GitHub DNS check should pass and you should be able to hit the Save button. It is also strongly recommended to enable HTTPS for your custom domain by checking the Enforce HTTPS box.

After a moment your static website should be accessible via your new domain. 🐙


My Website is not Accessible via the Custom Domain

Patience. Updating and propagating new DNS records can take quite some time. This makes iterating a tedious task, but using the above-mentioned dig command helps verify that things are set up as intended.

Each Commit to my Repo seems to break the configured Domain Routing

In case a push/commit to your repo containing the source code of your static website seems to break the DNS configuration, you might need to add a CNAME file to your repo. Usually, configuring the custom domain on the GitHub Pages settings tab will add a CNAME file to the branch from which your static page will be deployed. However, a GitHub Action could be implemented in such a way, that it would overwrite the CNAME file with every commit. If this is the case, you would need to add the file manually to your repo. To do so, have a look at the deploy branch of your repo (usually gh-pages) to conclude which folder of your source code branch will be deployed from the deploy branch. In the root of this folder, you have to add a file called CNAME (all uppercase). The content of the file must contain a single line only, which is the custom URL to point to your GitHub Page. In the case of this blog, here is the CNAME file which contains For more details have a look at the GitHub Troubleshooting docs.