Parents
Limit one game while preserving the school sign-in a household still needs.
DNS blocklists, one service at a time
Decide what stays off your network.
Build a blocklist for a game, store, or app and use it with Pi-hole or AdGuard Home. See which domains it covers, how we know, and what else it might break.
See what a list covers. Browse reviewed services and preview the rules before you apply them.
How it works
From “not that game” to a blocklist in three steps.
-
Pick the service
Search by name or vendor. Each entry names its boundary so the game, launcher, and store remain distinct.
-
Pick how firm
Conservative, Balanced, and Aggressive trade coverage against side effects. The evidence bar stays the same.
-
Subscribe once
Choose the format your DNS software accepts, test it locally, and undo it locally if it gets in the way.
Browse and preview reviewed services without an account. Sign in to save a list or set up a stable subscription where available.
Evidence in plain language
Every domain shows its work.
Each domain is labelled for the role it plays and how it was assessed. Terms such as known, observed, source-reported, and unverified explain the evidence in words.
- Core
- Needed to reach the service itself.
- Shared
- Also used by other services. We name them before you block.
- Auxiliary
- Login, updates, assets, or telemetry that may change how the service behaves.
- Tracker
- Tracking and analytics tied to the service.
Every firmness level uses the same evidence threshold. Unverified candidates stay held back.
Example Game at Balanced
Example data
-
Core Known
cdn.example-game.test -
Core Known
play.example-game.test -
Shared Source-reported
auth.example-id.testAlso serves Example Store and Example Chat. Left out at Conservative. -
Tracker Observed
telemetry.example-game.test
Who it is for
Made for the person who runs the network.
Small schools
See shared domains before a classroom tool gets caught in a broad block.
Libraries and clubs
Keep a shared network predictable with a version you can test and revisit.
Tinkerers
Choose plain domains, hosts, or supported Adblock-style rules and keep useful diffs.
Portable on purpose
Your DNS software. Your rules. Our research.
Works with what you own
Preview an export that matches the scope your Pi-hole or AdGuard Home can apply.
Links that stay put
Where subscriptions are enabled, renaming a saved list keeps its feed link intact. Each link keeps the format it was issued with.
Easy to undo
Try one change at a time. Remove the imported rules or subscription in your DNS software if you need to roll it back.
Example feed path
/feeds/{list-id}/{grant-id}/{token}/hosts
Example hosts output
0.0.0.0 assets.example.test
0.0.0.0 play.example.test
These are sample domains and placeholders. The feed itself contains only list output for your DNS client. Evidence and warnings stay in the preview and metadata.
Straight talk
Know the limits before you block.
What it is
Rules for the DNS software you operate, with the scope and collateral effects made visible.
What can still slip past
Encrypted DNS, another network, cached connections, changing domains, and shared infrastructure can all affect the result.
NotOnMyNet cannot uninstall an app, inspect traffic, or control a device away from this network.
Community-funded
Run on community support and donations.
We plan to keep the service free. Optional donations would help cover research, re-checking, and maintenance.