Instinctive

Get started with Instinctive

Sign in with a Google administrator account to get started

Get started with Instinctive

Sign in with a Google administrator account to get started

Upgrade to Instinctive District for this feature

Audit & fix Chrome settings to keep users safe & devices secure

Compare and sync settings across OUs or historical exports. Import settings to copy from one OU to another.

Unlimited search history

Batch actions (max. 250 items at a time)

Custom CSV exports for record-keeping

Hand Raise extension
<- Chrome Settings Library

EnableSha1ForLocalAnchors

Allow SHA-1 signed certificates issued by local trust anchors
Last updated October 8, 2024
Deprecated

When this setting is enabled, Google Chrome allows SHA-1 signed certificates as long as they successfully validate and chain to a locally-installed CA certificates. Note that this policy depends on the operating system certificate verification stack allowing SHA-1 signatures. If an OS update changes the OS handling of SHA-1 certificates, this policy may no longer have effect. Further, this policy is intended as a temporary workaround to give enterprises more time to move away from SHA-1. This policy will be removed on or around January 1st 2019. If this policy is not set, or it is set to false, then Google Chrome follows the publicly announced SHA-1 deprecation schedule.

Supported On:
Platform Start End
Android 54 71
Chrome (Windows, Mac, Linux) 54 71
ChromeOS 54 71
Example value:

false

Features: