Point Your naked Domain to WWW in Seconds

An apex domain (also called root, naked, or bare domain) is your domain without any prefix — for example example.com rather than www.example.com. Due to how DNS works, apex domains can't use CNAME records, which means they're incompatible with most CDNs and hosting platforms like GitHub Pages, Netlify, and Vercel. A redirect solves this by automatically forwarding apex visitors to your www subdomain where your site actually lives.

Just add two DNS records to your domain's apex (@):

That's it. No signup, no configuration. DNS changes typically propagate within 5–30 minutes, and SSL certificates are provisioned automatically.

Yes, HTTPS is fully supported and you don't need your own certificate. We automatically provision and renew SSL certificates via Let's Encrypt for every domain. Both http://example.com and https://example.com redirect securely to your www subdomain.

Completely free, no catch. No hidden costs, no premium tiers, no usage limits, no account required. We run on energy-efficient ARM64 infrastructure which keeps costs near zero, and we believe basic internet plumbing like domain redirects should be free for everyone.

Yes. The full path, query parameters, and fragments are preserved. For example, example.com/pricing?plan=pro redirects to www.example.com/pricing?plan=pro. This is a 301 permanent redirect, so search engines will transfer SEO value to your www URLs.

Absolutely — that's one of the most common use cases. Point your www subdomain to your hosting provider (e.g. a CNAME to username.github.io), then use ApexToWWW to redirect the apex domain to www. Works with GitHub Pages, Netlify, Vercel, Heroku, Firebase Hosting, Render, Fly.io, and any other platform that requires a CNAME.

It helps SEO. We use a 301 (permanent) redirect, which tells search engines to transfer ranking signals to your www URL. This consolidates your domain authority instead of splitting it between two addresses. Google recommends picking one canonical version (www or non-www) and redirecting the other — which is exactly what ApexToWWW does.

Our redirect servers run on dedicated infrastructure with high availability. The redirect itself is a simple, stateless HTTP response (<50ms) with no database or complex logic involved. Since it's a 301 permanent redirect, browsers also cache it locally — so even in the unlikely event of downtime, returning visitors would still reach your www site.

For most sites, www is the better choice. It supports CNAME records (required by most CDNs and hosting platforms), enables better cookie isolation between your main site and subdomains, and makes load balancing and domain migration easier. The important thing is to pick one and redirect the other — having both active without a redirect splits your SEO and confuses browsers.