![]() ![]() Additionally, if you have users that take their company-issued notebook home or on the road, the HOSTS file will still be there protecting your endpoint from ad/malicious servers. The advantage of this, versus say a browser extension, is that you are able to centrally manage this from your Windows Server and your users, for the most part, will not be able to "disable" it. This setup is essentially an alternative implementation of an ad blocker. The other content of your web page will still load, and the spots where the ad would have been displayed will typically collapse (at least for responsive websites) so you don't end up seeing voids. By pairing these ad server with a loopback address, a computer will query itself for the ad content and end up coming empty handed.įor example, if a web page you are visiting contains a script that calls an external ad server, such as the example shown below, as long as is listed in your HOSTS file with an IP of 127.0.0.1, no content will be delivered by. ![]() If it finds a matching hostname, it will use the IP address that's paired to it. When resolving hostnames, a computer by default will initially search its HOSTS file for the IP address. ![]() ![]() This is accomplished with the loopback address 127.0.0.1. It is a list containing thousands (at least for my project implementation) of ad servers - all are prevented from going out to the Internet to fetch ad content. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |