GoGuardian Admin Launches URL Matching for More Precise Rule Enforcement

Website URL rules could historically match more than intended. For example, a rule for “example.com” could also catch a lookalike domain like “example.com.evil-site.net”. URL Matching fixes this automatically. Qualifying new hostname rules now receive a trailing “/”, creating a clear boundary at the end of the hostname so rules match only the domain you intended.

Close the Glomming Loophole: Lookalike or proxy hostnames that merely begin with an allowlisted domain, like “example.com-badproxy.net”, no longer match your intended allow rule.

Filter by Top-Level Domain, Reliably: Rules like “*.edu/” now reliably target every site within a specific top-level domain, without unintentionally catching unrelated or longer domains.

Know Exactly What a Rule Will Match: A clear hostname boundary makes rule behavior predictable, so what you write is what gets enforced.

Nothing Changes for Existing Rules: Only new qualifying rules get the trailing slash automatically. Your existing Website URL rules are untouched.

Note: Auto-Format Domains is enabled by default for new rules entered in the Website URLs field. Admins who prefer to keep the previous matching behavior for new rules can disable the toggle at the policy level.

Learn more.

‍