Plenty of domain owners set up forwarding on yourdomain.com, test it, and move on — never noticing that www.yourdomain.com shows an error or, worse, a registrar parking page. A large share of visitors still type the www out of habit, and every printed link, business card, and radio mention may include it.
The two classic www failures
- No DNS record for www. The apex forwards; www doesn't resolve at all.
- A certificate that only names the apex. www resolves but the browser throws a certificate mismatch warning before any redirect happens.
Both are silent killers: you test the version you set up, and the other version fails only for real visitors.
How urlpath.cloud handles www
When you add a domain, the dashboard shows you the records for both the root and www — point them and you're covered on both names. The Let's Encrypt certificate that gets issued automatically includes the apex and www in one certificate, so neither name can trigger a warning. And redirects serve on both names: whether someone types yourdomain.com or www.yourdomain.com, they get the same fast, correct destination.
A bonus if you host DNS with us
The apex of a domain can't hold a CNAME record under DNS rules, which is why some hosts struggle at the root. The www name has no such restriction — it's the natural place for a CNAME when you're pointing domains at other infrastructure. Our DNS hosting addon supports records on both, so you can wire whatever mix of root/www pointing your setup needs.
Quick test
After pointing a domain, open both https://yourdomain.com and https://www.yourdomain.com (https, explicitly). Both should land on your destination with a padlock and no warning. If either doesn't, it's usually a missing DNS record — the dashboard's DNS check will show you which.