One of the most popular items here that I wrote back to very early 2010 is the mysterious 1e100.net. You may want to read before you read the rest of this for reference. That the article has been viewed thousands of times from people who want to know what the hell [subdomain] .net addresses.
There is only one way to block 1e100.net whole closely, and that is with two firewall rules based on the router. There is no way to block the 1e100.net completely through any adjustment in a browser or add on/extension. You can have NoScript, FlashBlock, Ghostery running at the same time, and 1e100.net will still make connections. If you have other products of Google as Google Talk, Picasa and Google Earth to name a few, 1e100.net is displayed. If you subscribe to RSS feeds that are basis of FeedBurner, using 1e100.net. If you have installed Google Chrome browser, a process in the background (at least in Windows) connects periodically to 1e100.net for updates. And even if you have installed without the udpater auto, chrome browser browser “phones home” three times to 1e100.net at each startup of the browser.
Then of course there are mountains of web sites (including this one) that uses Google Analytics to monitor traffic on the site. That there are many sites that use scripts through googleapis.com to the functionality of the site.
The vast majority of 1e100.net public IPs are in the range of 220.127.116.11 through 18.104.22.168 and 22.214.171.124 through 126.96.36.199.
If desired, you could block all these IPs with your router admin program.
Here is an example of a firewall rule:
This literally translates to is, “for all assigned by the router IPs in all ports, deny access to 188.8.131.52 through 74.125.255. 254?.” Called “Google 1? and the second range of IPs” Google 2?.
In my router in particular, the final part of an IP address cannot be 0 or 255, hence the reason by the shown as 1 and 254 above.
When these two rules are in effect, 99% of Google’s content is blocked. I say 99% because there are other Google IPs blocks is the owner of other services that have.
Your internet experience will be significantly limited.
YouTube will not work. Gmail will not work. Many web sites that use googleapis.com will not work. Google search will only work of species.
You can really see how deep Google permeates itself over the internet when you actually block their IP ranges of 1e100.net. It breaks a lot of things, and for this reason that I do not recommend is blocking his IPs.
I’ve seen many forum threads over the internet where a lot of people who monitor your personal network traffic are all asking the same thing: “how to block ** ALL ** Google?” Well, now you have your answer. Mostly. Lock the two IP ranges mentioned through your router, and the majority of connections 1e100.net stops cold.
Again I say that I do not recommend the blocking of Google in this way will be broken because a lof of things you use on the internet.
How do you know that the block is working?
Download TCPView and run it.
Go to your web browser and load YouTube, a Google property.
Immediately will be a lot of connections to 1e100.net in TCPView:
Enable the firewall in the router rules.
Close your browser and restart it, then try to load again youtube.com.
This is what will happen in TCPView:
Rather than ESTABLISHED, you will see SYN_SENT, which means that a connection is being Treaty. But the connection will never end because it is locked. When you see a lot of SYN_SENT s [nothing]. 1e100. net, the firewall rules are working.
If so, join more than 28,000 people who receive our exclusive weekly newsletter and advice of team and get free copies of 5 eBooks that we have created as our gift to you for subscribing. Simply enter your name and email address below: