Return IP to client for a dynamically created temporary web page that shows a Ticketmaster.com ad with a countdown of 10 seconds and javascript redirect to the actual taylorswift.com IP
Google is way ahead of you, they are a certificate authority now, so in theory they can do this right now. Take a look at any site’s https certificate and a significant portion of them are now signed by Google Trust Services LLC thanks to Cloudflare using them to generate free https certificates (in addition to letsencrypt). Note that they won’t ever pull this trick though because it’ll irreversibly damage their reputation.
I think they wouldn’t do that, since they could do the redirect within Chrome itself. The only reason they would do this is to grab users on other browsers, but that would mean everyone else stopping to use Google DNS, which means less data to collect or sell.
The only reason they would do this is to grab users on other browsers,
Yes that would be the purpose.
but that would mean everyone else stopping to use Google DNS, which means less data to collect or sell.
I agree, which is why I also agree with you why they haven’t done it yet, but I was speaking to how they could do it, not the fallout from them doing so.
I think they could 🤔
It would be trivially easy.
Request for www.taylorswift.com
Return IP to client for a dynamically created temporary web page that shows a Ticketmaster.com ad with a countdown of 10 seconds and javascript redirect to the actual taylorswift.com IP
But, HTTPS certificates.
Unless they provided overrides for their ads in Chrome, but at that point why do it with DNS.
Google is way ahead of you, they are a certificate authority now, so in theory they can do this right now. Take a look at any site’s https certificate and a significant portion of them are now signed by Google Trust Services LLC thanks to Cloudflare using them to generate free https certificates (in addition to letsencrypt). Note that they won’t ever pull this trick though because it’ll irreversibly damage their reputation.
I think they wouldn’t do that, since they could do the redirect within Chrome itself. The only reason they would do this is to grab users on other browsers, but that would mean everyone else stopping to use Google DNS, which means less data to collect or sell.
Yes that would be the purpose.
I agree, which is why I also agree with you why they haven’t done it yet, but I was speaking to how they could do it, not the fallout from them doing so.