Browse Policies & Filtering
- Application categories (Zero Trust app management)
- Active Directory group policies
- Content categories
- Custom block pages
- Don't mix DNS providers
- Prevent DNS bypass
- Safe Search explained
- Safe Search supported search engines
- Security categories
- Working with policies
- Working with allow and block lists
- YouTube Restricted Mode explained
YouTube Restricted Mode explained
How ScoutDNS enforces YouTube's three restriction levels (Strict, Moderate, Unrestricted), what each one blocks, and how Google Workspace settings interact with ScoutDNS network policy.
ScoutDNS can enforce YouTube’s built-in restriction modes at the DNS layer, so videos that YouTube classifies as inappropriate are filtered at the platform level. You don’t need a Google Workspace (formerly G Suite) account to use this feature.
[!NOTE] ScoutDNS applies restriction at the network level, it affects every YouTube viewer behind the policy. Individual videos can’t be allowed or blocked by URL. Google Workspace settings always win over network settings, so if a Workspace admin has set a different YouTube mode for their domain, that mode applies to those users.
The three modes
| Mode | What it does | Recommended for |
|---|---|---|
| Strict | Most restrictive. Filters out many videos via YouTube’s automated system. Live streaming and comments are disabled. | Elementary school-aged children |
| Moderate | Less restrictive, much larger video catalog available. Live streaming and comments are still disabled. | High school-aged students |
| Unrestricted | No YouTube-level filtering applied. | Adult or unrestricted-access populations |
[!IMPORTANT] Both Strict and Moderate disable live streaming and comments, not just adult content. This is YouTube’s policy, not a ScoutDNS choice.
All filtering decisions are made by YouTube’s own algorithm using automated classification plus user reports. ScoutDNS only signals which mode to apply, the actual content judgment is YouTube’s.
Configure in ScoutDNS
YouTube Safe Mode is set per policy:
- Open the policy → Settings tab.
- Under Base Settings, pick the mode in the YouTube Safe Mode dropdown.
- Save.
The change applies to every WAN, profile, or persona using the policy.
Workspace + ScoutDNS together
If your organization runs Google Workspace, Workspace admin settings take precedence. To control YouTube via Workspace, see Google’s documentation on YouTube settings for Workspace admins.
Pattern that works well:
- Workspace sets the floor for managed accounts (signed-in students/staff).
- ScoutDNS network policy sets the floor for unmanaged accounts (signed-out users, guest devices, BYOD).
Troubleshoot
[!WARNING] YouTube’s restriction state can be cached in browser and app storage after you change the policy. If a device looks stuck on the previous mode, clear:
- The OS DNS cache (
ipconfig /flushdnson Windows,sudo dscacheutil -flushcacheon macOS)- The browser cache for
youtube.com- The YouTube mobile app cache (Settings → Apps → YouTube → Storage → Clear Cache)
You can verify which mode is active for the current device at youtube.com/check_content_restrictions.
For Google’s own reference on the modes themselves, see the YouTube Restriction FAQ.
Related
- Working with policies
- Safe Search explained, adjacent Google/Bing content control
- Browser HTTPS errors, needed for clean block-page rendering when restricted videos are blocked