Blocking a particular site in IE7

Is there a way to block a web site in IE7. When the user types in the address I want it to respond with unable to find site or unable to connect to site or something like that?

My daughter's friends come over and go to a particular site and I want to block it.

Is there an easy way?

Can I add a redirect in my hosts file????

 

Got it in the Hosts file. All is well.

Thanks

Mitch

 

Understood. It would be somewhat funny though, a year from now going crazy trying to load a site, uninstalling-reinstalling to no avail.....

But not to worry....no one from this house will ever be going to that site.

Mitch

 

Hi, guys.

On my Win XP Home SP2, [FONT= "Courier New"]127.0.0.1 yahoo.com[/FONT] in the HOSTS file will block access to http://yahoo.com but it will not block access to http://www.yahoo.com

Therefore, Mitch, you might want to add entries to the HOSTS to cover all bases.

EDIT: Depending on how computer-savvy your daughter and her friends are (assuming you have them use a Guest account), I suggest you also make the HOSTS read-only or otherwise limit their ability to view/modify the HOSTS file.

 

so far so good. Added an *. in front of the last part of the domain just in case there were other similar sites.

Tested it with yahoo.com and couldn't get to mail.yahoo.com so hope it is working... history so far has shown things to be working the way I want them to.

Mitch

 

Hi, Mitch.

In case you aren't aware of the MVPS HOSTS file, here's a link to information. (If you use Windows Vista, be sure to also read the Windows Vista information.)

MVPS also states,

Here's a direct link to the MVPS hosts.zip file.

If you rename your current HOSTS file to HOSTS.OLD and then unzip the MVPS HOSTS file to the same folder, that HOSTS file will help prevent access to many unknown-to-you "questionable" sites.

You can then add your own custom 127.0.0.1 entries to that file as well. (Just be sure your custom-made entries are AFTER the 127.0.0.1 localhost entry, which must be first in the list in any HOSTS file you use.)


NOTE: If you use SpySweeper, according to MVPS,

Also...

Depending on how much you trust your daughter and her friends, if you (or a willing friend) have administrative access to a web server somewhere that your daugther and her friends are highly unlikely to visit, then you could create custom HOSTS entries (for *.yahoo.com or whatever) with the web server's IP address instead of 127.0.0.1 and periodically review the web server's connection logs to see if connections were made from your own computer's IP address.

This idea would work best if your computer has a static (non-changing) IP address (as in some broadband accounts).

If your computer's IP address changes frequently (in a dial-up account, for example), then you could cross-reference your computer's connection logs to the web server's connection logs. Norton SystemWorks (NSW), for example, has a "Connections" viewer in its "Norton Internet Worm Protection" section.

A locally-installed connection log utility might even negate the need for administrative access to a web server.

If you don't use NSW, then perhaps free connection log utilities are available on the net that will suit your needs. If you want to investigate this route, then please let us know and I'll see what I can find. I like tinkering with different utilities so it would probably be fun for me.