Lots of nonsense here. Google routinely generates new ssl certificates with low TTLs. Anycast DNS will yield changing IP addresses over time and also between ne

Lots of nonsense here. Google routinely generates new ssl certificates with low TTLs. Anycast DNS will yield changing IP addresses over time and also between networks. Netscape-remote sounds like something that hails back to the Netscape 4.x era where, I believe, there was a command line argument to open a web page in an existing browser session by specifying -remote and the URL. 1e100(.net) is the value for a "googol" and it's pretty well known to be used in google's reverse DNS. And I can totally see sha1 still in use to maximize browser support, especially for a web page that is likely set as browser homepage on millions of outdated computers and android 2.x era phones. Anyways, don't use reverse DNS to try to determine IP ownership - looking up the netblock owners in WHOIS is much better.