I'll try But in case I get lazy (which is likely what will happen) or don't have much time, here are the basics.
Instab has already posted some of the offending strings here. There's more than one "clientsn.google.com" domain, and the page translator, which by design is a call-home itself, uses "translate.googleapis.com". It's not a good idea to pad anything with null bytes (0x00), as that usually makes the browser crash. Replace them with 0.0.0.0, http://0.0.0.0/ or https://0.0.0.0/, respecting the original format used by each string.
Furthermore, under Vista and above, additional requests come in the form of multicast DNS, which you probably don't need anyway (it's for small networks without centralized name resolution). You can turn it off by applying the following registry tweak and rebooting.
While not directly related, I have also turned off WebRTC device enumeration, SCTP Data Channels, local device discovery and local printing in chrome://flags. The first two may be why the IP leak test can't find my addresses.Code:REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient] "EnableMulticast"=dword:00000000
Of course, Iron's source code is open so you could remove the offending requests directly from the code and recompile, but this takes less time.
That's undeniably true. I switched to Firefox three years ago and was stunned by the extent to which you can personalize things - altering UI elements via CSS, where else can you do that? Unfortunately, the Gecko engine is so slow when compared with, well, everything else. The slower speed was ultimately a killer for me
Bookmarks