Comment by phoghed 14 days ago You ISP also collects and sells data to companies like Moz, and possibly to Google too. 5 comments phoghed Reply soblemprolver 14 days ago URL paths over https wouldn't be transparent to the ISP though, would they? throw10920 14 days ago They would not - GP was probably bringing up something not directly relevant, but still related. (they should have clarified though) edoceo 14 days ago What can I add? I know the domain could be found. But how did Google index a page that is example.com/$MD5.html - guessing 128bit numbers is hard.I have visited that page from a signed-in Chrome profile. 1 reply → phoghed 14 days ago That assumes it was using it from the get go and every time, which might not be a safe assumption.
soblemprolver 14 days ago URL paths over https wouldn't be transparent to the ISP though, would they? throw10920 14 days ago They would not - GP was probably bringing up something not directly relevant, but still related. (they should have clarified though) edoceo 14 days ago What can I add? I know the domain could be found. But how did Google index a page that is example.com/$MD5.html - guessing 128bit numbers is hard.I have visited that page from a signed-in Chrome profile. 1 reply → phoghed 14 days ago That assumes it was using it from the get go and every time, which might not be a safe assumption.
throw10920 14 days ago They would not - GP was probably bringing up something not directly relevant, but still related. (they should have clarified though) edoceo 14 days ago What can I add? I know the domain could be found. But how did Google index a page that is example.com/$MD5.html - guessing 128bit numbers is hard.I have visited that page from a signed-in Chrome profile. 1 reply → phoghed 14 days ago That assumes it was using it from the get go and every time, which might not be a safe assumption.
edoceo 14 days ago What can I add? I know the domain could be found. But how did Google index a page that is example.com/$MD5.html - guessing 128bit numbers is hard.I have visited that page from a signed-in Chrome profile. 1 reply →
phoghed 14 days ago That assumes it was using it from the get go and every time, which might not be a safe assumption.
URL paths over https wouldn't be transparent to the ISP though, would they?
They would not - GP was probably bringing up something not directly relevant, but still related. (they should have clarified though)
What can I add? I know the domain could be found. But how did Google index a page that is example.com/$MD5.html - guessing 128bit numbers is hard.
I have visited that page from a signed-in Chrome profile.
1 reply →
That assumes it was using it from the get go and every time, which might not be a safe assumption.