I still use www. subdomain on my websites, but omit it for domains that are not meant to be visited by people browsing internet (e.g. “api.example.com”, or web applications (more complex websites that are not for just scroll-and-read, e.g. “example.app” or app.example.com).
Are you afraid your browser will send an email there instead of browsing?
Anyway, I’m firmly on the team that thinks if you are making a site, you should redirect the www into your address. No point in leaving the few users that write it by hand lost. But there isn’t a good reason to put complicate your address with it either.
The first time I tried it with the www dot but it didn’t work. I guess at some point we stopped being on the World Wide Web.
I still use www. subdomain on my websites, but omit it for domains that are not meant to be visited by people browsing internet (e.g. “api.example.com”, or web applications (more complex websites that are not for just scroll-and-read, e.g. “example.app” or app.example.com).
If you go to the port 443, you are already on the www. There’s no need to say it.
There’s also no need to point to automatic ATM machines either.
I don’t like address implications, that will eventually lead to errors.
Are you afraid your browser will send an email there instead of browsing?
Anyway, I’m firmly on the team that thinks if you are making a site, you should redirect the www into your address. No point in leaving the few users that write it by hand lost. But there isn’t a good reason to put complicate your address with it either.