Deprecating automatic .com redirects

Back in 2020 we moved all sites from being served under *.netlify.com to being under *.netlify.app. This was to isolate customer sites from ones run by Netlify, trying to minimize the confusion. In doing this, we built in an automatic redirect for subdomain.netlify.com to subdomain.netlify.app to avoid downtime on customer sites. Now most sites either use the .app url directly, or have a custom domain.

Starting on Friday March 29th, 2024, new sites won’t be getting this behavior as we begin phasing it out. This means that your older sites will continue redirect from *.netlify.com to *.netlify.app, but new sites will not. Our plan is to fully deprecate the feature by the end of April.

What this means for you is really, nothing much! If you’ve got a site that is accessible by subdomain.netlify.app, it will continue to be fully reachable. If your link is to subdomain.netlify.com, it will stop redirecting in May. You’ll need to use the .app url.

If you’re using a CNAME linked to subdomain.netlify.com, generally, you’ll wanna update that to be for your .app domain, but it will continue to work for DNS.

If you’re running into problems with this, please post in this thread or contact support for help.

1 Like

We mentioned in late March (forums post) that we’ll be finishing the deprecation of the automatic redirection from *.netlify.com to *.netlify.app. New sites haven’t been using it for about a month. As of May 1st 2024, we will finish this deprecation.

This is hopefully a big ole nothing sandwich for most folks. We’ve seen that most sites will use the [subdomain.netlify.app](<http://subdomain.netlify.app>) URLs directly. If you’re not, the old [subdomain.netlify.com](<http://subdomain.netlify.com>) urls will start returning a 404.

If you’re using a CNAME linked to subdomain.netlify.com, generally, you’ll wanna update that to be for your .app domain, but it will continue to work for DNS.

If you’re running into problems with this, please post in this thread or contact support for help.

I guess some will have problems. Like me, I have printed many flayers, stickers, cards… for an event in my university and the domain name written is that site with “.com” now it won’t work anymore and money wasted on those printed stuff. I you can get back to the old redirection version, it will be helpful for users!

Some students like me who works on some non-profit projects will have big issues!

Hi @mohamedyanis, that’s really unfortunate. However, this change cannot be reversed at this point. I am sorry to break it to you, but it sounds like the print material is now going to return a 404 as well.

Exactly, the site written on the materials is going to return a 404 page.

This isn’t a new thing @mohamedyanis. New sites have used netlify.app since 2020 (original announcement post now hidden) which means you’ve had 4 years to ensure everything has the .app domain and not the .com domain and/or use a custom domain.

Yes I know, I’m talking about the automatic redirection. Before, when we use “.com”, it will automatically redirect the site to “.app”. Now, it won’t work anymore. I didn’t know that this feature will be removed one day.

Unfortunately, Netlify will not revert this change and the .com URLs will return 404s.

The public docs and the website have only said netlify.app then entire time your account has existed. These changes were made before your login at Netlify or any of your sites have been created. Yes, we were still 301 redirecting .com to .app until recently but all documentation and UI elements have said netlify.app the entire time you have used our service.