Can a single domain be deleted from HSTS list through GPO


+ A single domain can be deleted from the HSTS (HTTP Strict Transport Security) list through Group Policy Objects (GPO).
+ The process involves editing the registry on the client computer and configuring a GPO to remove the specified domain.
+ This solution is suitable for organizations that need to manage their HSTS settings centrally.


+ The HSTS list is a browser-maintained list of domains that have enabled HTTPS, and it helps enforce the use of secure connections for those domains.
+ However, sometimes it may be necessary to remove a domain from the HSTS cache on client computers.
+ In this article, we will explain how to delete a single domain from the HSTS list using GPO.

– Steps to Delete a Single Domain from HSTS List through GPO
1. Edit the Registry
+ Open the registry editor on the client computer by pressing Windows key + R, typing “regedit”, and hitting Enter.
+ Navigate to the following key: `HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet SettingsDomains`.
+ Locate the subkey that corresponds to the domain you want to remove from HSTS.
+ Right-click on the subkey and select “Delete”.
2. Configure GPO
+ Open the Group Policy Management Console (GPMC) by typing “gpmc.msc” in the Start menu search box or Run dialog.
+ Create a new GPO linked to the Organizational Unit (OU) that contains the client computers you want to apply the policy to.
+ Right-click on the new GPO and select “Edit”.
+ Navigate to `Computer ConfigurationAdministrative TemplatesWindows ComponentsInternet ExplorerSecurity Features`.
+ Double-click on “HSTS site list” and set it to “Disabled”.
3. Apply the GPO
+ Close the Group Policy Editor.
+ Wait for the GPO to be applied to the client computers (this may take some time).
+ Verify that the domain has been removed from the HSTS list on the client computers by checking the registry key again or using a tool like Fiddler.


+ Deleting a single domain from the HSTS list through GPO can be useful in situations where a website has been compromised or when testing changes to a site that requires HTTPS.
+ This solution is straightforward and can be implemented by IT administrators without requiring advanced knowledge of security policies.
+ However, it’s essential to carefully consider the impact of removing a domain from HSTS before implementing this solution.

Previous Post

Does your ISP know what type of phone/computer you’re using?

Next Post

Authentication flow leading to wrong authenticator app – what happened and how to prevent?

Related Posts