Analysis updated 2026-07-09 · repo last pushed 2025-01-09
Show a clear message to your family when a DNS filter blocks a website on your home network.
Demo how Structured DNS errors could improve browser UX for content filtering.
Test what the DNS block experience looks like across different websites using AdGuard DNS.
| adguardteam/dns-sde-extension | aiecosvietnam/aiecos-social-crm | rafaelferreira2312/devforge | |
|---|---|---|---|
| Stars | 15 | 15 | 15 |
| Language | HTML | HTML | HTML |
| Last pushed | 2025-01-09 | — | — |
| Maintenance | Stale | — | — |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 2/5 | 3/5 | 1/5 |
| Audience | developer | pm founder | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires manual setup in Chrome developer mode and must be paired with a specific AdGuard DNS configuration.
This browser extension, created by AdGuard, is a proof-of-concept that shows what happens when a website is blocked by a DNS filtering service. Normally, when a DNS blocker stops you from visiting a site, you just see a generic browser error that looks like the site is broken. This extension replaces that confusing error with a clear, custom page explaining exactly why the site was blocked. Here is how it works. When you try to visit a website, the extension watches for loading errors on the main page. If it detects that a site failed to load, it checks with the AdGuard DNS service to see if the site was intentionally blocked. If it was, the extension shows a detailed block page instead of the standard error message. The project uses Structured DNS errors, a way for DNS services to pass along readable information about why a block happened, rather than just returning a simple failure. This tool is mainly for developers, browser makers, and tech enthusiasts who want to see how Structured DNS errors could improve the web browsing experience. For example, a parent using DNS filtering to block adult content on their home network could use this to show their kids a clear message about why a site is blocked, rather than a vague technical error. It demonstrates how browsers could natively handle DNS blocks in a more user-friendly way. It is important to note that this is a demonstration project, not a finished product for everyday users. It requires manual setup in Chrome's developer mode and needs to be paired with a specific AdGuard DNS configuration. The project trades ease of use for a focused look at a specific technology, serving as a working example of what native browser support for detailed DNS blocking could look like.
A browser extension by AdGuard that replaces confusing browser errors with clear messages when a website is blocked by DNS filtering. It is a demo of Structured DNS errors showing why a site was blocked.
Mainly HTML. The stack also includes HTML, Browser Extension, Chrome Extension APIs.
Stale — no commits in 1-2 years (last push 2025-01-09).
No license information is provided in the repository, so usage rights are unclear.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.