Dimitar Nestorov
Established Member
- Impact
- 10
Google Chrome refuses to visit the new .app domains without https
If classic Google PPC monetization - forget about such redirects, this is prohibited by Google.in order to redirect them to global parking services
Thanks for keeping an open mind...@Donny - thanks. You make some great points. And yeah getting there.
@Michael M - very true indeed. The future definitely is in HTTPS. Actually, as with .app domains, even the present is now with HTTPS. So a solution is definitely required either sooner or later.
It won't hurt for us to look into it while taking all of Donny's great points into account.
It reminds me when people were buying .tel domains to find out they couldn't park them
https://www.do.tel/faqs/do.tel/faqs/ said:If you do not wish to use the free Telhosting service, that is fine as you can use your .tel for any purpose of your choosing e.g. hosting your own website.
It does not appear to have any scaling issues that I have noticed so far. I guess we will see if no services offer SSLs for .app and thousands sign up for my forwarding service. I personally am hoping they all figure it out so I don't have to deal with any scaling issues since it's free.LetsEncrypt will be hard to scale for thousands of domains.
In fact, setting up SSL is not the problem, the problem is to gather the private certificates and automate the deployment.
...
Just need to automate the LetsEncrypt part. (emphasis added to your sentence)
.app is definitely going to be a challenge for domainers.
Yes, now you can use your own name servers but until recently you couldn't. A domain name that can't be used for a website or other Internet service like E-mail is useless right. And now domainers are stuck with plenty of .app domains that they can't host readily.That was only back in the day?
Not saying it can't be done but tedious and challenging. Of course the easy way for a parking company or hosting company would be to become a certification authority, then you can roll out certificates easily and domain validation poses no problem.Challenges arise every day as technology evolves. But this is just a first indication of the need for all services to provide SSL to appease Google and new tech.
I have a little over 100 SSLs/sites setup in the 1 day my .app forwarding website has been online. All automated and no issues. Interested to see if it keeps going smoothly as it scales - but I see no reason why it would not.cPanel partnered with Comodo to release a feature called AutoSSL. Basically the same as LetsEncrypt but the issuer is Comodo. I used to have LetsEncrypt in my cPanel and then one day it disappeared.
I made a reverse IP lookup on my website and found 785 websites hosted on our IP address. Cool thing is that I tried a bunch of them by manually writing https in the address bar and they all resolved with
Which means that my hosting provider has SSL setup for 785 domains just on that server. If cPanel can do it, so can you!
I used to have LetsEncrypt in my cPanel and then one day it disappeared.
I made a reverse IP lookup on my website and found 785 websites hosted on our IP address. Cool thing is that I tried a bunch of them by manually writing https in the address bar and they all resolved with
Which means that my hosting provider has SSL setup for 785 domains just on that server. If cPanel can do it, so can you!
I totally understand the difference in scale. But hosting providers do manage to do this without issue.Let me know when you can add four or five million.
I'll wait...
Donny
Let me know when you can add four or five million.
I'll wait...
Donny
Agreed. If landing/parking companies had to buy an SSL cert for each domain they would go out of business.Cloudflare bought their own CA. This is why they can offer universal SSL. I think any parking company would offer ssl if it was possible and still profitable. Buying an SSL cert for every parked domain isn't a reality.
I would give you a Google lava lamp and two packs of bubble gum.
Donny
I would give you a Google lava lamp and two packs of bubble gum.
Agreed. But you wouldnt point your nameservers to my webservers during testing so I was going to throw those in as an added bonus.Nameservers have nothing to do with SSL. It's all done on the webserver.
Donny
Cloudflare bought their own CA. This is why they can offer universal SSL. I think any parking company would offer ssl if it was possible and still profitable. Buying an SSL cert for every parked domain isn't a reality.
I would give you a Google lava lamp and two packs of bubble gum.
Donny
I doubt that would work for them as cloudflare isnt going to want to issue them 5 millions SSLs for free. Their "universal SSL" isn't exactly universal. It is just offered to each customer per site from my understanding.I'm not sure what you're using for dns right now but if you'd be willing to work with cloudflare you could use that advantage.
They're easy to integrate into any backend. You deliver the panel, they take care of the rest. Again, it might take a lot of rewriting of your current system but I think in the long run it's worth it.
I doubt that would work for them as cloudflare isnt going to want to issue them 5 millions SSLs for free. Their "universal SSL" isn't exactly universal. It is just offered to each customer per site from my understanding.
And their DNS option, is really just a redirection solution in a nutshell. And we can't work with redirection.
Donny
Possible future blocks of sites without SSL from browsers