block by roachhd f69d3d4baa12bae1d4c1

Faster github pages, from the GitHub blog.


Faster, More Awesome GitHub Pages · GitHub

We just rolled out some big improvements to GitHub Pages. Now, when someone visits a Pages site, rather than GitHub serving the content directly, the page is served by a global Content Delivery Network, ensuring that the nearest physical server can serve up a cached page at blazingly fast speeds. As an added bonus, we can now protect your GitHub Pages site with the same kind of Denial of Service mitigation services used for

If you are using a subdomain, custom subdomain, or an A record with GitHub Pages, you may need to make some changes.

Default User Domain -

Default subdomains are automatically updated by our DNS, so we’ve got you covered.

Custom Subdomain ( - with CNAME

If you are using a custom subdomain (like, you should use a CNAME record pointed at as described in our help document.

Apex domain ( - with ALIAS or A

If you currently use an A record, you can tell if you need to move if your A record is pointed to or You can check using:

$ dig    7200  IN  A


$ dig    7200  IN  A

Some DNS providers (like DNSimple) allow you to use an ALIAS record to point your custom apex domain to If your DNS provider supports this configuration, it will allow us to provide the full benefits of our Content Delivery Network and Denial of Service protection to your Pages site.

If you switch to a subdomain or switch to a DNS provider that supports ALIAS records, you can take advantage of the Content Delivery Network and Denial of Service mitigation.

If you are using an apex domain (e.g. instead of a subdomain (e.g. and your DNS provider does not support ALIAS records, then your only option is to use A records for your DNS. This configuration will not give your Page the benefit our Content Delivery Network, but you will still be protected by our Denial of Service mitigation. Configure your A or ALIAS records as described in our [help article].

Happy (and faster) publishing!