Designed not to alter your network stack.
GuardianBlock is built for adult Windows accountability without installing a DNS resolver, creating a VPN, changing firewall rules, editing hosts, changing proxies, routes, adapters, SMB mappings, mapped drives, WSL mounts, or work-network configuration.
The boundary is the point.
GuardianBlock is designed around a local Windows service, supported-browser policy, protection health, and accountability signals. That means the product boundary deliberately excludes the network surfaces people often rely on for broad filtering.
- DNS resolver configuration
- VPN profiles or tunnel routing
- Windows Firewall rules
- Hosts file entries
- System proxy configuration
- Routes and network adapters
- SMB mappings and mapped drives
- WSL mounts and work-network configuration
Why we draw the line there.
Many adults use the same personal Windows device for normal life, local development, travel, or work. GuardianBlock's job is accountability for the person who opted in, not taking ownership of their whole network path or breaking unrelated tools.
A narrower technical surface, stated honestly.
This boundary is not a claim that GuardianBlock sees every possible path to a gambling site. It is a product choice: focus on supported browsers, local device posture, signed policy, and keyholder-visible health rather than becoming a DNS, VPN, firewall, proxy, or network appliance.
This is a design boundary, not a universal coverage claim: GuardianBlock's blocking scope is browser and device posture based, and unsupported browsers remain outside private-beta blocking scope.
- It avoids taking over traffic that belongs to a workplace, VPN, router, or local development setup.
- It makes device-health changes visible to the accountability relationship instead of pretending the network layer is invisible friction.
- It keeps public wording tied to the evidence we still need to capture in clean Windows VMs.
How this differs from DNS, VPN, and network filters.
The comparison is about architecture, not brands. Network filters can be the right tool for a household or an organization; GuardianBlock is deliberately aimed at voluntary adult Windows accountability.
DNS/VPN/network filters: broad network path, can conflict with VPNs/work networks, not GuardianBlock's design.
GuardianBlock: supported-browser policy + local service + health/accountability, no network-stack mutation by design.
What has to be verified before the public claim graduates.
The page stays out of search while that evidence is unfinished. We would rather leave a trust page noindex than publish a stronger work-network safety claim before the full lifecycle has been captured.
The public claim remains evidence-gated until clean Windows 11 Home and Pro VM snapshots prove the full install, activation, update, rollback, and uninstall lifecycle leaves those settings alone.
- Clean pre-install snapshots for Home and Pro
- Post-install and activation snapshots
- Update and rollback snapshots
- Supported uninstall lifecycle snapshots
- Diff review for DNS, VPN, firewall, proxy, hosts, routes, adapters, SMB, mapped drives, WSL mounts, and work-network settings
Last reviewed 2026-06-29
Related trust pages: FAQ and privacy overview.
Want the accountable version, not a network appliance?
Join the private-beta waitlist if you want GuardianBlock's Windows accountability model and its honest network boundary as the evidence fills in.