Origins or hostname patterns for which restrictions on insecure origins should not apply
Explanation
Setting the policy specifies a list of origins (URLs) or hostname patterns (such as *.example.com) for which security restrictions on insecure origins won't apply. Patterns are only accepted for hostnames; URLs/origins with schemes must be exact strings. Organizations can specify origins for legacy applications that can't deploy TLS or set up a staging server for internal web development, so developers can test out features requiring secure contexts without having to deploy TLS on the staging server. This policy also prevents the origin from being labeled "Not Secure" in the address bar.
Setting a list of URLs in this policy amounts to setting the command-line flag --unsafely-treat-insecure-origin-as-secure to a comma-separated list of the same URLs. The policy overrides the command-line flag and UnsafelyTreatInsecureOriginAsSecure, if present.
For more information on secure contexts, see Secure Contexts ( https://www.w3.org/TR/secure-contexts ).
Example value:
http://testserver.example.com/
*.example.org
Registry
HKEY_LOCAL_MACHINE\Software\Policies\Google\ChromeHKEY_CURRENT_USER\Software\Policies\Google\Chrome- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Computer (HKLM)
Enable
# Enable: chrome/OverrideSecurityRestrictionsOnInsecureOrigin
$k = 'HKLM:\Software\Policies\Google\Chrome\OverrideSecurityRestrictionsOnInsecureOrigin'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Origins or hostname patterns for which restrictions on insecure origins should not apply
# Non-additive list: existing values of the key are cleared first
if (Test-Path -Path $k) { (Get-Item -Path $k).Property | ForEach-Object { Remove-ItemProperty -Path $k -Name ([WildcardPattern]::Escape($_)) -ErrorAction SilentlyContinue } }
$values = @('<value1>', '<value2>') # Replace the values with your own
$i = 1
foreach ($v in $values) { Set-ItemProperty -Path $k -Name ('' + $i) -Value $v -Type String; $i++ }Disable
# Disable: chrome/OverrideSecurityRestrictionsOnInsecureOrigin
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": chrome/OverrideSecurityRestrictionsOnInsecureOrigin
$k = 'HKLM:\Software\Policies\Google\Chrome\OverrideSecurityRestrictionsOnInsecureOrigin'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Origins or hostname patterns for which restrictions on insecure origins should not applyOverrideSecurityRestrictionsOnInsecureOriginDesc | List (table)list | Software\Policies\Google\Chrome\OverrideSecurityRestrictionsOnInsecureOriginValues named “” + number | REG_SZ (values under the key) |
Application
Google Chrome (Google) — November 2026 templates
Official templates downloaded on November 12, 2026.