Skip to main content
Exceptions allow specific websites, applications, and IP addresses to bypass GoGuardian filtering. Use them when resources required by your organization experience unexpected behavior due to GoGuardian’s local proxy. A Super User or custom role can manage exceptions in Org Management.

​
Understand How Exceptions Work

Exceptions are used when applications or websites experience unexpected behavior, including:
  • Websites that fail to load all elements or resolve
  • Websites with SSL pinning that cause connection delays
  • Applications that cannot open
  • Resources blocked by Admin policies that must remain accessible, such as direct IP addresses or subdomains
Exceptions still pass through GoGuardian’s local proxy when The GoGuardian App is installed, but are not filtered by GoGuardian Admin policies. Exceptions can take up to five minutes to apply. Once active, they supersede policies in GoGuardian Admin, GoGuardian Beacon, and GoGuardian Teacher — the resources are no longer filtered.
GoGuardian and Google domains are hardcoded exceptions and do not need to be added manually.

​
Identify Resources to Add as Exceptions

Before adding exceptions, review the Diagnostics log in Org Management to identify which resources are being blocked. Diagnostics show HTTP/HTTPS traffic blocked in the last 24 hours per user, including the blocked URL, event type, and recommended next steps. Common resources to add as exceptions include:
  • CDN URLs
  • Subdomains used by web applications or single sign-on (SSO) authentication
  • Low-traffic websites blocked by Admin policies or unable to establish a secure connection with GoGuardian
See Troubleshoot with Diagnostics to pull a blocked traffic log for a specific user.

​
Add Hostname Exceptions

Hostname exceptions exempt specific domains or subdomains from GoGuardian filtering across all browsers and apps.
  1. Go to manage.goguardian.com and select Installations.
  2. Select The GoGuardian App, then choose Manage Exceptions.
  3. Select Hostname Exceptions.
  4. Enter one domain or subdomain per line. Use full domain format (example.com) or subdomain format (sub.example.com).
  5. Click Save.
  6. Verify the result: The hostname appears in your exceptions list. Changes take up to five minutes to apply.
[screenshot: Hostname Exceptions field in Org Management with example domain entries] Best practices for hostname exceptions:
  • Add wildcards for both the root domain and subdomain when a site has multiple services: example.com and *.example.com. Adding only one does not automatically apply to the other.
  • Prefix subdomain exceptions with a wildcard and period (*.apple.com) to prevent access to misleading websites. Do not use *apple.com without the period.
  • Avoid wildcards on both sides of a domain (*.example.com*) to prevent unexpected behavior.
Add Hostname Exceptions

​
Configure Application Exceptions

Application exceptions automatically exempt the required domains for commonly used cloud applications. Toggling on an application exception is faster than identifying and entering individual domain exceptions manually.
  1. Go to manage.goguardian.com, select Installations, then select The GoGuardian App.
  2. Select Manage Exceptions, then select Application Exceptions.
  3. Turn on the toggle for each application to exempt.
  4. Verify the result: The toggled applications appear as active in your exceptions list.
Applications available for automatic exception:
  • Adobe Creative Cloud
  • Apple App Store
  • Classlink
  • Clever
  • Edmentum - Study Island
  • Google Classroom
  • Google Play Store
  • Microsoft Office
  • Microsoft Store
  • Microsoft Teams
  • Pearson
  • Seesaw
  • Zoom
Configure Application Exceptions

​
Add IP Exceptions

IP exceptions exempt specific static IP addresses from GoGuardian filtering. Use these for network infrastructure resources such as printers that use fixed IP addresses.
  1. Go to manage.goguardian.com, select Installations, then select The GoGuardian App.
  2. Select Manage Exceptions, then select IP Exceptions.
  3. Enter each IP address and click Add.
  4. Verify the result: The IP address appears in your exceptions list.
Add IP Exceptions

​
Set Up Windows Application Exceptions

Windows application exceptions exempt specific local application files — such as executables and dynamic-link libraries — from GoGuardian filtering on Windows devices. Requires The GoGuardian App 1.22.0 or later.
  1. Go to manage.goguardian.com, select Installations, then select The GoGuardian App.
  2. Select Manage Exceptions, then select Windows Exceptions.
  3. Enter each file path and click Add.
  4. Verify the result: The file path appears in your Windows exceptions list.
[screenshot: Windows Exceptions field with example executable path entries] Best practices for Windows application exceptions:
  • Add specific app files, including executables (.exe) and dynamic-link libraries (.dll)
  • Include the deepest child path or use a wildcard to match it — child paths do not inherit parent exceptions. Example: C:\Program Files\Vendor\*
  • Separate path segments with backslashes (\). Example: C:\Program Files\Vendor\app.exe
  • Prefix each path with a drive letter (C:\) or two backslashes for a UNC path (\\server\share\folder)
  • Limit wildcards (*) to trusted paths or variable-name paths, such as apps that change install paths after updates
  • Keep paths to 255 characters or fewer
  • Exclude invalid characters: < > ? " |
  • Keep Allow Native Apps enabled to allow native Windows applications and reduce troubleshooting
Set Up Windows Application Exceptions

​
Resources

Troubleshoot with Diagnostics

Review blocked traffic logs to identify resources that need exceptions.

Understand The GoGuardian App on Windows

Review Windows-specific feature behavior and hostname exception context.

Review Roles and Permissions

Confirm which roles can manage exceptions in Org Management.
Last modified on July 14, 2026