How to block a specific website on Windows

You can block one website on one Windows PC in about two minutes by editing the hosts file, and it will work. It also only covers that PC, only until someone undoes it, and it does not stop the next site. Here is the manual method, honestly, and then the version that survives contact with a real family.

What’s the quick manual way?

Windows keeps a small text file that maps website names to addresses, and it gets checked before anything else. Point a name at nowhere and the PC stops finding it.

1. Open Notepad as an administrator. Right-click it in the Start menu and choose Run as administrator. This matters, because the file cannot be saved otherwise.
2. Open C:\Windows\System32\drivers\etc\hosts. You will need to switch the file-type dropdown to All Files to see it.
3. Add a line at the bottom: 0.0.0.0 example.com, then another for 0.0.0.0 www.example.com. The www version is a separate name and needs its own line.
4. Save. The block takes effect immediately, though an already-open browser tab may need a refresh.

That is the whole technique. It works on any Windows PC and it costs nothing.

So why doesn’t that solve the problem?

Because of what it doesn’t do. Four things, and they compound.

• It covers one PC. The laptop is blocked. The other laptop, the tablet, and the phone are not. Your child’s homework machine and their bedroom machine are separate jobs.
• It covers one name. You blocked one site. The same content lives at a hundred other addresses, and the site you blocked may have three names of its own. You are playing whack-a-mole with a text file, and the moles are automated.
• It is trivially reversible by an administrator. If your child’s account has admin rights, they can open the same file and delete the line, and nothing will tell you they did. This is the single biggest gap, and it is worth fixing whatever else you do: put your child on a standard account.
• Nothing notices when it stops working. A Windows update, a system restore, or a cleanup tool can wipe the entry. You will find out when something gets through.

Manual blocking is a fine answer to “there is one specific site and one specific PC and I need it gone tonight”. It is not an answer to “I want the family’s devices to be safe”.

What actually holds?

The same idea, moved to a better place. Every app on a PC finds a website by looking the name up first, so a filter at that lookup covers every browser and every app at once, not just the one you thought of. Move that lookup off the machine and onto a filtered service, and you get three things the hosts file cannot give you: it applies to every device on the plan, it uses a maintained list of millions of sites by category instead of the lines you typed by hand, and it runs above your child’s account so a standard user has no file to edit.

The full explanation of that design, and why it travels with the laptop off your home Wi-Fi, is in how DNS filtering protects every device.

Which should I use?

Use the hosts file if you have a one-off: one site, one PC, right now, and you are happy to redo it if it gets wiped. It is genuinely the fastest tool for that job.

Use device-level filtering if what you actually want is for the family’s PCs to be safe by default, without you maintaining a list, and without it quietly coming undone. That is not a settings problem, it is a layer problem, which is the same reason browser-based parental controls fail.

FamilyProtect filters at the lookup, on every Windows PC in your home, on one plan. It sets itself up in a few minutes (here’s how) and repairs itself if anything drifts. Start your 14-day free trial, or see what is covered on pricing.