For IT admins rolling PhishClean out to staff browsers. The admin page generates ready-made files for most of this; this guide explains each route and what to check afterwards.
You need: your organisation key (pc_org_…, shown on the admin page) and admin rights in whichever tool manages your browsers.
| Browser | Extension ID | Update URL |
|---|---|---|
| Chrome (and Brave) | kloceclooedmphmnnpgoekolaggejgca | https://clients2.google.com/service/update2/crx |
| Microsoft Edge | jeilenifcaoenlglebpmmphbfmbfkgbj | https://edge.microsoft.com/extensionwebstorebase/v1/crx |
| Firefox | phishclean@phishclean.com | https://addons.mozilla.org/firefox/downloads/latest/phishclean/latest.xpi |
Two policy values configure the extension:
orgKey (string): puts the browser on your plan. Every check is on, with no sign-up, trial or payment prompts for the user.trustedDomains (list of strings, optional): domains PhishClean never warns about, such as your own SSO and internal sites. Subdomains are included.{ "orgKey": { "Value": "pc_org_YOUR_KEY" }, "trustedDomains": { "Value": ["yourcompany.com"] } }chrome://policy and press Reload policies.Settings catalog (recommended): Devices → Configuration → Create → Windows 10 and later → Settings catalog.
jeilenifcaoenlglebpmmphbfmbfkgbj;https://edge.microsoft.com/extensionwebstorebase/v1/crx.
For Chrome, use Google Chrome → Extensions → Configure the list of force-installed apps and extensions with
kloceclooedmphmnnpgoekolaggejgca;https://clients2.google.com/service/update2/crx.orgKey, trustedDomains) are not in the catalog. Deploy the PowerShell script from the admin page (Devices → Scripts and remediations → Platform scripts, run as system, 64-bit), or the .reg file. Both write them under HKLM\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\<ID>\policy and the Google\Chrome equivalent.Import the .reg file from the admin page through a GPO (Computer Configuration → Preferences → Windows Settings → Registry), or use the Chrome and Edge ADMX templates for the force-install list plus the 3rdparty registry values for the settings.
Deploy a configuration profile for the preference domain com.google.Chrome (or com.microsoft.Edge) with ExtensionInstallForcelist set to the ID;update-URL string above, plus a second payload for the extension's managed storage containing orgKey and trustedDomains. The admin page shows the exact keys.
Add this to policies.json in the Firefox distribution folder, or through your MDM's Firefox policy support:
{
"policies": {
"ExtensionSettings": {
"phishclean@phishclean.com": {
"installation_mode": "force_installed",
"install_url": "https://addons.mozilla.org/firefox/downloads/latest/phishclean/latest.xpi"
}
},
"3rdparty": {
"Extensions": {
"phishclean@phishclean.com": { "orgKey": "pc_org_YOUR_KEY", "trustedDomains": ["yourcompany.com"] }
}
}
}
}
If you already have a policies.json, merge these two sections into it.
chrome://policy, edge://policy or about:policies and confirm the force-install entry and the extension's policy values.Nothing to set up and no sign-up. They see warnings on dangerous pages and a weekly summary notification. Managed installs never show the rating prompt, the trial or the individual paywall.
Remove the extension from the force-install list. Browsers uninstall it at their next policy refresh.
PhishClean for Teams is $5 per user per month or $50 per user per year, minimum 5 users. The pilot is free for 30 days and needs no card.
See PhishClean for TeamsLast updated: