Paste the domains you want gone and download a ready-to-install hosts file or uBlock filter list.
A hosts file is the quietest blocking tool on any device: a local address map that points chosen domains to nowhere. Paste the domains you want blocked and this generator builds a ready-to-install file (for Windows, macOS or Linux) or a uBlock Origin filter list for the browser extension.
Generated entirely in your browser: the list never leaves your device. Pair it with the per-device blocking guides on this site for the full setup, and read the blocker comparison guide to understand what a hosts file can and can't do.
A hosts file is a local address map that your device checks before it asks the internet where a domain lives. Every line pairs a domain with an address. When the address is a dead end, the domain simply never loads.
That is the whole mechanism. No software runs in the background, no account is needed, and the block applies to every program on that device that uses normal name resolution. It is the quietest blocking tool there is, which is also why it is easy to forget you installed one.
The generator has a checkbox that merges a community-maintained adult domain list into your file. The list comes from the StevenBlack hosts project, a public block list that has been maintained for years. The page shows the live count, so you always know how many domains the preset adds.
The list is stored in encoded form and only decoded when you actually generate the file. Nothing from the list, and none of your own domains, is sent anywhere. The generator works entirely in your browser and hands you the finished file as a download.
The preset is optional. You can generate a file from your own list alone, or mix both: your hand-picked domains plus the community list in one file. The checkbox is the only difference between the two outputs.
Your device resolves names in a fixed order, and the hosts file is checked before the network is even asked. A domain you put in the file gets pointed at the loopback address, and requests to it go nowhere. That is why the block feels instant: the device never leaves your machine to fail.
Two honest limits. The file matches exactly what you wrote, so misspellings slip through and the block does not extend to similar names. And if a browser or app uses its own encrypted DNS, it may resolve the name itself and walk around the file. Most software does not, but the exceptions exist, and they are worth knowing before you trust the file blindly.
On Windows the file lives at C:\Windows\System32\drivers\etc\hosts and you need administrator rights to edit it. Open Notepad as administrator, open the file from that path, append the generated lines, and save. On macOS and Linux the path is /etc/hosts, edited with sudo.
After saving, test one blocked domain by opening it in a browser or pinging it. If it still loads, your edit did not save, or the browser is one of the encrypted-DNS exceptions. Checking one domain after install takes ten seconds and saves a lot of false confidence.
A hosts file blocks names, not traffic. A VPN tunnel that resolves names on its own server will simply not consult your file. An app with a hardcoded address has no name to look up. And the file only covers the one device it is installed on, so every other device on your network needs its own copy or a different tool.
That is why the honest framing is one layer of several. The hosts file is a strong first wall because it is free, local and instant, but it was never meant to be the only wall. Pair it with a DNS filter on the router for the rest of the household, or with the browser-level tooling in the blocking guides.
The three tools cover different ground. A hosts file is per-device and permanent until you edit it again. A DNS filter on the router covers every device on the network with one setting, but follows you nowhere when you leave the house. A browser extension blocks inside the browser only, and is the easiest to disable in a weak moment.
The practical order for most people: router DNS for the household, hosts files on the devices you personally control, and the built-in platform filters from the blocking guides as the final layer on phones. Every layer has a different removal cost, and that cost is what makes the stack hold.
Blocking closes a doorway, and closing doorways works. It does not by itself change the pull behind the doorway. The tools on this site treat the two problems separately: the blocking guides handle the doorways, and the quit tracker plus urge surfing handle the pull, with a day count and a log of the hard minutes.
Set up the block, then start the tracker on the same day. The combination gives you a measure of both halves: the block keeps the worst hours out of reach, and the tracker shows you, in days, what the extra distance did.
Windows: C:\Windows\System32\drivers\etc\hosts, opened in Notepad as administrator. macOS and Linux: /etc/hosts, edited with sudo. Append the generated lines at the end, save, and test one blocked domain afterwards.
No. It blocks exactly the domains you list, matched literally. VPN traffic and apps with hardcoded addresses can bypass it. Treat it as one layer, and combine it with router DNS filtering or the platform settings in the blocking guides.
No. The generator runs entirely in your browser. Your list is merged locally, the finished file comes down as a download from your own machine, and nothing you paste is ever sent to a server.