Skip to main content
CleanWeb

DNS filtering, without the black box.

A cleaner network starts with a list you can inspect.

Generate filtering files for AdGuard Home, Pi-hole, and hosts files — with named sources, visible rules, and a syntax check before download. No account, no rule uploads.

  • Browser-only processing
  • Licenses shown up front
  • No account required

Configuration draft

Privacy · Balanced · AdGuard Home

3 decisions

Included categories

TrackingAds
format sampleAdGuard
! CleanWeb configuration
! Target: Privacy | Strength: Balanced
! Sources: named + licensed
! Domains: built in your browser

||example.org^

Syntax illustration, not a generated blocklist. Real files carry full source and license headers.

Source snapshotOct 20, 2026

9

named source categories

Each with a license and upstream link

41,904

bounded snapshot entries

Up to 5,000 per category

0

rules sent to a server

Validation and generation run locally

Three useful tools

See the rules. Check the rules. Track the changes.

CleanWeb is deliberately narrow: it helps you build, inspect, and compare DNS filtering files. It does not hide the list behind a dashboard.

01

Generate

Choose a goal, software, and strength. Get one file in the right syntax, with every source and limitation printed into the header.

Goal: Privacy
Software: Pi-hole
Strength: Balanced
Create a configuration
02

Validate

Paste or open a blocklist. Find invalid hostnames, duplicates, empty lines, conflicts, and syntax your DNS tool will ignore — with line numbers.

Invalid hostnameLine number included
Duplicate ruleFirst occurrence shown
Format detectedAuto-detection badge
Open the validator
03

Compare

Put an old and a new list side by side. See exactly what was added, removed, or duplicated before you overwrite a working setup.

+

Added

−

Removed

=

In both

2×

Duplicates

Compare two lists

How it works

Three decisions. One inspectable file.

You do not need to understand DNS rule syntax to start. You do get to see exactly what will be installed.

  1. 1

    Pick the filtering goal

    Privacy, Family, or Security. The interface shows which source categories come with each strength.

  2. 2

    Choose the software

    AdGuard Home, Pi-hole, or a hosts file. The output syntax changes; formats are never merged.

  3. 3

    Preview and self-check

    Inspect the header and first rules. CleanWeb reparses its own output for syntax, duplicates, and limits.

  4. 4

    Download, then install

    Copy or download the exact file. Follow the software-specific guide and keep a rollback path.

Supported software

Different tools. Different syntax. No guesswork.

CleanWeb only emits a format when it can state the syntax and the installation path. Local file installation varies by software and version.

Network-wide filtering

AdGuard Home

Native AdGuard-style DNS rules. Add the generated file as a local filter or from a private URL.

||example.org^AdGuard Home guide
Network-wide filtering

Pi-hole

A domain-only list for Pi-hole's adlist workflow. Add it as a local adlist, then rebuild gravity.

example.orgPi-hole guide
One device at a time

Hosts file

IPv4 mappings for a single computer. Exact hostnames only — no wildcard subdomains or network-wide sync.

0.0.0.0 example.orgHosts file guide

Source transparency

No mystery lists.

Every category is tied to a real upstream list, a recorded license, a snapshot count, and a check date. The source snapshot is checked into this project; it is not fetched silently during your visit.

Unlicense / MIT. The Block List Project repository declares the Unlicense; some file headers state MIT.

Bounded by design. Up to 5,000 hostnames per category are included, clearly labeled as a starter snapshot.

No invented rules or stats. If a source cannot be verified, the configuration is not marked ready.

Source snapshot

Checked Oct 20, 2026

Active upstream
  • Ads

    Unlicense

    5,000 entries
  • Tracking

    Unlicense / file: MIT

    5,000 entries
  • Malware

    Unlicense / file: MIT

    5,000 entries
  • Phishing

    Unlicense / file: MIT

    5,000 entries
  • Scams

    Unlicense / file: MIT

    5,000 entries
  • Ransomware

    Unlicense / file: MIT

    1,904 entries
+ 3 more categories on the source page.

Read before you install

Plain-language setup guides.

Each guide explains the actual file workflow, what the software can and cannot do, and where versions differ. No fake screenshots, no skipped prerequisites.

FAQ

The honest answers.

DNS filtering is useful, but it is not magic. These are the limits you should know before changing your network.

Is CleanWeb a DNS resolver?

No. CleanWeb generates filtering files and checks lists; it does not answer DNS queries. You still need a resolver such as AdGuard Home or Pi-hole to apply the rules.

Do my pasted rules or uploads leave my browser?

No. The validator and diff tools read files with the browser File API and process them in the tab. There is no upload endpoint. The generator only fetches CleanWeb's own static source snapshots from the same site.

Will this block every advertisement?

No. DNS filtering only sees hostnames. It cannot inspect paths inside an encrypted page, most in-app content, or traffic from devices that ignore your chosen resolver. It can also block something you need. Treat it as one layer, not a guarantee.

Are the filtering lists complete mirrors of upstream lists?

No. Each source category is a bounded starter snapshot of up to 5,000 hostnames. The source page shows the upstream totals where reported and links to the complete lists. The generated file includes the same caveat.

Which file should I download?

Pick the software that already handles DNS for your network. AdGuard Home and Pi-hole receive network-wide filters. A hosts file only affects the device where you install it. CleanWeb never mixes syntaxes in one output.

Can I use the rule data commercially?

The Block List Project repository declares the Unlicense, and some source list headers state MIT. Both permit commercial use. CleanWeb records the exact source and license, but you should review upstream terms and notices for your own distribution.

Ready when you are

Build a filter you can explain.

Make three choices and get one clearly labeled file. Or bring an existing list and find out what is actually in it.