LiveChat 
Support 
How to Block a Website: Every Method for Devices, Networks, and Your Own Site
When someone searches for “how to block a website,” they’re usually after one of two completely different things. Some people want to stop a site from loading on their own computer or home network, maybe to keep kids off something inappropriate, or to stop themselves from doom-scrolling during work hours. Others run a website and want to block *other people* from reaching *their* site, usually spammers, scrapers, or attackers.
Same phrase, opposite jobs. This guide covers both, clearly separated, so you can jump to whichever half you actually need. I’ll keep it plain and practical, with the exact steps and a couple of copy-paste code snippets.
Key Takeaways
• “Block a website” means two opposite things: stopping your device or network from reaching a site, or stopping unwanted visitors from reaching your site.
• To block a site on your device, edit the hosts file, install a browser extension, or use OS parental controls.
• To block a site across a whole household, use router-level blocking or a content-filtering DNS resolver.
• To block unwanted visitors from a site you own, use `.htaccess` deny rules, cPanel’s IP Blocker, or a server firewall.
• Figure out which end of the connection you’re on first. The tools live at opposite ends.
The single most useful thing to understand here is that “block a website” splits into two opposite jobs that people constantly conflate. One job is stopping yourself or your network from reaching a site. That’s access control on *your* end of the connection, and it happens at the device, DNS, or router level. The other job is stopping a site’s unwanted visitors from reaching you. That’s defending *your* site, and it happens at the server level through firewalls and `.htaccess`. They use completely different tools sitting at opposite ends of the same connection. So before you do anything, figure out which end you’re on. If the goal is distraction control or parental safety, you work on the device or DNS. If the goal is stopping spam or attacks on a site you run, you work on the server’s firewall and `.htaccess`. The phrase is identical; the solutions are mirror images.
Which kind of “blocking” do you actually need?
Before picking a method, match your goal to the right side of the connection. This table sorts the common reasons people want to block a website and points each one at the best approach.
| Your goal | Which end? | Best method |
|---|---|---|
| Keep a child off a specific site | Your device/network | Router blocking or OS parental controls |
| Stop yourself visiting a distracting site | Your device | Browser extension or hosts file |
| Filter adult content across the whole house | Your network | Content-filtering DNS resolver |
| Block one site on a single work laptop | Your device | Hosts file |
| Stop a spammer hammering your contact form | Your site (server) | `.htaccess` IP deny or cPanel IP Blocker |
| Stop scrapers and bad bots stealing content | Your site (server) | Firewall + bot blocking |
| Block visitors from a whole country | Your site (server) | Server/network firewall (country block) |
If your goal is in the top half, read Part A. If it’s in the bottom half, jump to Part B.
Part A: How do you block a website on your own device or network?
This is the “I want to stop a site from loading here” side. There are four solid routes, ranging from a single device to your entire home.
How do you block a site by editing the hosts file?
Every computer has a small text file called the hosts file. It maps website names to addresses *before* your computer asks the internet. If you point a site’s name at `127.0.0.1` (your own machine, which has no website there), the site simply fails to load. It’s free, built in, and works without any extra software.
On Windows, open Notepad as an administrator and open:
“` C:\Windows\System32\drivers\etc\hosts “`
On Mac or Linux, edit the file at:
“` /etc/hosts “`
Then add a line for each site you want to block. Use both the bare domain and the `www` version:
“` 127.0.0.1 example.com 127.0.0.1 www.example.com “`
Save the file. The block takes effect almost immediately, though you may need to close and reopen your browser. To unblock, just delete those lines.
The hosts file is great for one or two sites on one machine. It’s less great for a long list, and anyone with admin rights can simply edit it back, so it’s not a strong parental control on its own.
How do you block a website with a browser extension?
If you only care about blocking sites inside your web browser, a site-blocking extension is the easiest option. Most major browsers have free extensions that let you type in a list of sites to block, set schedules (for example, block social media from 9 to 5), and password-protect the settings.
This is the friendliest choice for productivity and focus. The catch: it only blocks within that one browser. Open a different browser or an app and the block is gone. For self-discipline that’s usually fine; for locking down a device it isn’t enough.
How do you block a site for the whole house using your router?
To block a site on every device in your home at once, including phones, tablets, and games consoles, you block it at the router. The router is the box that connects your whole home to the internet, so a rule there covers everything connected to it.
The steps vary by router brand, but the pattern is the same:
- Open a browser and go to your router’s admin address (often `192.168.0.1` or `192.168.1.1`, usually printed on the router).
- Log in with the admin password (also often on a sticker on the device).
- Look for a section called Parental Controls, Access Restrictions, URL Filtering, or Website Blocking.
- Add the site addresses you want to block, and save.
Router blocking is the strongest household-wide option because it doesn’t depend on any one device cooperating. The downside is that router menus differ a lot between brands, and basic routers sometimes only allow a short list of blocked sites.
How do you block sites across your network with DNS filtering?
DNS is the internet’s phone book: it turns a website name into the numerical address your device connects to. A content-filtering DNS resolver is a phone book that simply refuses to look up sites in categories you’ve blocked, such as adult content, gambling, or known malware.
You set it up by changing the DNS server addresses on your device or, better, on your router so it covers everything. Several free and paid content-filtering DNS services exist, and many let you pick which categories to block from a dashboard.
DNS filtering is excellent for category-based blocking (“block all adult sites”) rather than naming sites one by one, and it covers the whole network when set at the router. The limitation is that it filters by category and known lists, so a brand-new site might slip through until it’s categorized.
How do you block websites with built-in parental controls?
Both major desktop and mobile operating systems include parental controls (sometimes called Family settings or Screen Time). These let a parent account block specific sites or whole categories, set time limits, and stop a child from changing the rules. Because they’re tied to a user account, they follow the child across that device rather than relying on a single browser.
If your main goal is child safety on a specific phone, tablet, or laptop, this is usually the most robust single-device option, because it’s designed to resist being switched off by the person it’s restricting.
If you want to understand how the underlying address-lookup layer works in more depth, that’s a good moment to read up on the wider basics of how hosting and the web fit together.
Part B: How do you block unwanted visitors from a website you own?
Now the other half. You run a site, and you want to keep specific people, bots, or whole regions *out*. This is server-side work, and the tools live on your hosting account rather than on your laptop.
Why would a site owner block visitors at all?
A few very common, very practical reasons:
- Spam. A single bot hammering your comment section or contact form from one address.
- Attacks. Repeated login attempts or probing from a known-bad IP.
- Scrapers. Bots copying your content or pricing wholesale.
- Bandwidth abuse. Aggressive crawlers eating server resources and slowing your real visitors.
Blocking these doesn’t just tidy up your inbox; it protects performance and security for everyone else.
How do you block an IP address with .htaccess?
If your hosting runs on an Apache web server (most shared hosting does), you can block visitors using a file called `.htaccess` in your site’s root folder. It’s a plain text file that gives instructions to the server.
To block one or more specific addresses, add:
“`apache
The first line lets everyone in by default; the `Require not ip` lines carve out the addresses you’re banning. The `/24` on the second one blocks a whole range, handy when an attacker hops between nearby addresses.
On older Apache setups you may instead see the classic syntax:
“`apache
Order Allow,Deny Allow from all Deny from 203.0.113.45 “`
Edit the wrong line in `.htaccess` and you can take your whole site offline, so always keep a backup copy before changing it.
How do you block an IP using cPanel’s IP Blocker?
If hand-editing files makes you nervous, most hosting control panels include a point-and-click tool. In cPanel it’s called IP Blocker (sometimes “IP Deny Manager”). You type in a single address or a range, click a button, and the control panel writes the correct `.htaccess` rule for you behind the scenes.
This is the easiest, safest way to ban a visitor because there’s no syntax to get wrong. For most site owners blocking the occasional spammer, IP Blocker is all you’ll ever need.
How do you block bots, countries, and bigger threats with a firewall?
For anything beyond a handful of addresses, you want a firewall, the security guard that inspects traffic before it reaches your site. A good firewall handles the cases `.htaccess` struggles with:
- Bot blocking by recognizing bad crawlers and automated attack patterns.
- Country blocking when you only serve one region and the abuse comes from elsewhere.
- Rate limiting to stop a single source flooding you with requests.
Server-level and network-level firewalls do this automatically and at scale, without you maintaining giant block lists by hand.
Here’s how the site-owner methods compare:
| Method | Best for | Difficulty |
|---|---|---|
| cPanel IP Blocker | Banning a few specific addresses | Easy |
| `.htaccess` deny rules | Specific IPs and ranges, custom rules | Medium |
| Server/network firewall | Bots, countries, attacks, rate limits | Handled for you |
Where does DarazHost fit in?
If you’re on the site-owner side of this, you shouldn’t have to build all this protection from scratch. DarazHost gives site owners easy, built-in ways to block unwanted traffic: a cPanel IP Blocker for quick bans, full `.htaccess` rule support for custom control, and server and network firewalls with country and bot blocking. That means you can keep spammers, scrapers, and attackers off your site without becoming a security engineer overnight, and our 24/7 support is there if you’re not sure which rule to use. The protective controls are baked in, so the hard part is handled for you.
You can also read our complete guide to how web hosting works and how to choose a host to see how these security tools fit into the bigger picture of running a site.
How do you choose the right blocking method?
Walk through three quick questions:
- Which end am I on? Trying to stop a site from loading *here* (device/network), or stop visitors reaching a site *I run* (server)? This is the big fork.
- How wide does it need to be? One device, the whole house, one address, or whole categories and countries? Wider reach means moving up: from hosts file, to router, to DNS filtering, to firewall.
- Who might try to undo it? If a savvy teenager or a determined attacker is on the other side, pick the sturdier tools (account-based parental controls, router rules, server firewalls) over the easily reversed ones (a single browser extension or hosts file).
Answer those and the right method usually picks itself.
Frequently asked questions
Does editing the hosts file slow down my computer? No. The hosts file is checked instantly during normal address lookups, so adding a few blocked sites has no noticeable effect on speed.
Can someone get around a website block? It depends on the method. A browser extension or hosts file edit can be undone by anyone with access to the device. Router rules, account-based parental controls, and server firewalls are much harder to bypass, which is why they’re better for security and child safety.
Will blocking an IP address stop a determined attacker? Not always. A motivated attacker can switch addresses. Blocking a single IP stops casual abuse, but for persistent attacks you want a firewall that can spot patterns and block ranges or bot behavior automatically.
Is it better to block by category or site by site? For one or two specific sites, block them by name (hosts file, router, or extension). For broad goals like “no adult content anywhere,” category-based DNS filtering is far more practical than listing sites individually.
Can I block a whole country from my website? Yes, with a server or network firewall that supports geographic blocking. This is common for sites that only serve one region and see abuse coming from elsewhere. It isn’t something a basic hosts file or browser extension can do.
