Apex domain, it's also called naked domain, is a kind of domains without sub-domain.
I've been using it for my app, Inkdrop whose domain of the website was inkdrop.app but now it's moved to www.inkdrop.app.
I deploy it on Netlify which are often mentioned as a fast web hosting service.
I saw many websites performing very fast with Netlify, but my website didn't have such speed. Especially, the TTFB (Time-to-first-byte) was extremely long, usually longer than 200ms and it takes 800ms to transfer only 120KB. Why?
If you have your own domain, you have to configure a
CNAME record to point it to the Netlify's domain.
But Apex domain is not supported setting a
CNAME record by design.
To host a website with an Apex domain on Netlify, one option is to use
ALIAS record instead:
- Geo-targeting information is lost. Since it is the_authoritative_server forexample.com(issuing the queries forlb.example.net), then any intelligent routing functionality on thelb.example.netrecord will act upon the location of the authoritative server instead of your location. The EDNS0 edns-client-subnet option_does not_apply here. This means that you may be potentially mis-routed. For example, if you are in New York and the authoritative server forexample.comis in California, thenlb.example.netwill think you are in California, and will return an answer that is distinctly sub-optimal for you in New York.
ALIAS record, Netlify is not able to know where visitors are from or to optimize the traffic route.
I asked Netlify that it is due to
Unfortunately, that seems to be true.
I decided to move my website to
Apex domains look beautiful (for developers), but it seems like not a big deal for visitors.
I found that recent browsers strip
www from their address bar like Chrome:
As stated by a Chromium developer, the
m (for mobile) subdomains are being classified by Google as "trivial" subdomains because they feel most people do not need to be concerned with the information they represent.
I guess I am also not caring about
www subdomain when visiting websites because I didn't notice that Netlify's website is actually
So, it would be fine.
As you can see, it has been significantly improved after moved it to
As fool said above, you have two options at present:
- Netlify DNS hosting, since they can (and do) use linked A records which do allow geolocation
- Cloudflare’s CNAME flattening, since that does not seem to interfere with Netlify's geolocation
Why I didn't choose it is because I've already adopted NS1 and just switching to
www was the quickest way to solve my issue.
Hope that helps improve your website!