en-US chrome computer user

HTTP Allowlist

Verified with Google Chrome — updated on July 10, 2026 Supported on: Microsoft Windows 7 or later

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome

Registry

HKLM Software\Policies\Google\Chrome
HKCU Software\Policies\Google\Chrome

Other deployment channels

Intune (ADMX ingestion)
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Miscellaneous/HttpAllowlist

OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.

macOS / Linux preference HttpAllowlist
Android restriction HttpAllowlist
Supported platforms
  • Google Chrome (Android) — since version 112
  • Google Chrome (Linux) — since version 112
  • Google Chrome (Mac) — since version 112
  • Google Chrome (Windows) — since version 112
  • Google ChromeOS (Google ChromeOS) — since version 112
  • Google Chrome (Fuchsia) — since version 112

Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page

Options

HTTP Allowlist
List (registry values) list list under Software\Policies\Google\Chrome\HttpAllowlist

Description

Setting the policy specifies a list of hostnames or hostname patterns (such as '[*.]example.com') that will not be upgraded to HTTPS and will not show an error interstitial if HTTPS-First Mode is enabled. Organizations can use this policy to maintain access to servers that do not support HTTPS, without needing to disable HTTPS Upgrades and/or HTTPS-First Mode. Supplied hostnames must be canonicalized: Any IDNs must be converted to their A-label format, and all ASCII letters must be lowercase. Blanket host wildcards (i.e., "*" or "[*]") are not allowed. Instead, HTTPS-First Mode and HTTPS Upgrades should be explicitly disabled via their specific policies. Note: This policy does not apply to HSTS upgrades. Example value: testserver.example.com [*.]example.org

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO. ⓘ

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: HTTP Allowlist
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\HttpAllowlist]
; List values: enter one value per line in the builder UI.
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: HTTP Allowlist
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome\HttpAllowlist'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI.

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview