Salesforce is changing a long list of security rules. Some already changed; others change later. This page checks your org against every one of them and tells you, in plain words, what is broken, what is about to break, and what to do about it. It works with any org — Production or any kind of sandbox. It only reads. It never changes anything in your org.
https://mycompany.my.salesforce.com ·
Sandbox: https://mycompany--uat.sandbox.my.salesforce.com.
Paste the origin only — no path.
localStorage or sessionStorage. Closing this tab wipes it.
Logging in needs a connected app. You set one up once, and then use it against any org you audit. In the org you want to check:
(loading)
The access token you get back is held in memory only, expires on its own, and can be revoked by logging out. That is a smaller blast radius than a pasted Session ID, which carries your whole login.
document.cookie.split('; ').find(c=>c.startsWith('sid=')).slice(4)
on a *.my.salesforce.com tab (not a Lightning .lightning.force.com tab —
that cookie is a different, non-API session).The session must belong to a user with API Enabled. If Setup → Session Settings has Lock sessions to the domain in which they were first used enabled, use a session id taken from the same My Domain host you paste above.
Opening this file by double-clicking gives the page the opaque origin null, which the
Salesforce CORS allowlist generally will not accept. Pick one of these, in order of preference:
http://localhost:8000/security-audit-dashboard.html:
python -m http.server 8000
npx --yes http-server -p 8000Then in your org add that origin: Setup → Security → CORS → Allowed Origins List → New, Origin URL Pattern
http://localhost:8000.null as an origin pattern in
Setup → CORS. Some org configurations accept it; many do not.
A CORS failure shows up as “Failed to fetch” with no HTTP status. A wrong or expired session
id shows up as HTTP 401 INVALID_SESSION_ID — those are different problems.
Enforcement dates were compiled from the Salesforce Release Updates page, Winter ’27 release notes and the architect/developer release blogs. Salesforce postpones, re-scopes and cancels release updates, and some dates are reported inconsistently across sources — always confirm the date for your org in Setup → Release Updates before committing to a remediation plan.