Not a DNS blocker. Not a VPN. Not a firewall.
GuardianBlock blocks at the browser and device layer. It does not alter DNS, hosts, VPN, firewall, proxy, routes, adapters, SMB mappings, mapped drives, WSL mounts, or work-network configuration.
The boundary is the point.
GuardianBlock is built around a local Windows service, supported-browser policy, protection health, and accountability signals. The product boundary deliberately excludes the network surfaces people often reach for when they want 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: supported browsers, local protection health, signed policy, and status the accountability partner can see, rather than becoming a DNS, VPN, firewall, proxy, or network appliance.
This is a focused Windows boundary, not a universal coverage claim: GuardianBlock protects browsing in Chrome, Edge, and Firefox and blocks unapproved browser software from running as an alternate route on the protected Windows account.
- It avoids taking over traffic that belongs to a workplace, VPN, router, or local development setup.
- It keeps protection health and its limits visible to the accountability partner rather than hidden inside a network layer.
- It keeps our public promises limited to what GuardianBlock actually does.
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 this means for a work laptop
GuardianBlock blocks inside the browser and on the device, and does not alter the VPN, proxy, or mapped-drive settings a work setup depends on. A personally owned, unmanaged PC you also use for work qualifies when setup finds no device management or policy conflicts; an employer-managed device is out of scope.
Related pages: FAQ, privacy overview, and limitations.
Want the accountable version, not a network appliance?
Start GuardianBlock to set it up with an accountability partner you trust.