Secure context and cross-origin isolation
Flags telling whether the page is HTTPS and isolated from other origins.
In one line
Can check whether the page is on HTTPS and isolated, which describes the site, not you
Flags telling whether the page is HTTPS and isolated from other origins.
isSecureContext and crossOriginIsolated are set by the site itself, so they mostly describe the page, not the person. They gate high-power APIs and timer precision (5 microseconds when isolated, 100 microseconds otherwise in Chrome).
What it can and can't do
What the user does: Nothing. It describes how the site itself was set up
It can
- Check if the page runs on HTTPS
- Check if the page is isolated from other origins
- Unlock stronger features and finer timers when both are true
It cannot
- Tell anything about you or your device
- Be changed by you; the site sets it
- Unlock powerful features on plain HTTP pages
- Give you finer timers unless the site opts in
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 47 | 2015-12-01 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Supported | 49 | 2016-09-20 | None |
| Safari | Supported | 11.1 | 2018-04-12 | None |
| Safari on iPhone | Supported | 11.3 | 2018-03-29 | None |
| Chrome on Android | Supported | 47 | 2015-12-02 | None |
| Samsung Internet | Supported | 5.0 | 2016-12-15 | None |
How a site asks for it
| API | window.isSecureContext, window.crossOriginIsolated |
| Browser compat keys | api.Window.isSecureContextapi.Window.crossOriginIsolated |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
isSecureContext | boolean | None | true or false | Not listed |
crossOriginIsolated | boolean | None | true when COOP+COEP set | Not listed |
Technical limits
- Describes the page, not the user
The story
What it is
Two yes or no flags showing whether a page is on HTTPS and walled off from other sites.
For you
You never see these flags. They mostly describe how the site is built. If a site turns the isolation on, you may get faster, more powerful pages such as full speed browser games and editors.
For makers
Powerful features like shared memory and fine timers only work on pages that are secure and isolated. Heavy apps flip the switch to run fast. The flags describe the page rather than the person, so they carry little tracking value.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game engine needs isolation to use shared memory threads, so it runs at a smooth frame rate. | Unity WebGL games |
| creative | A browser video editor needs it to run fast video code in the page. | Clipchamp |
| developer | A web code editor runs a full programming environment in the tab, which needs the isolation flag. | StackBlitz |
| productivity | A browser version of a design app turns on advanced timers and threads for heavy files. | Figma |
| security | A bank locks down its pages so another site cannot peek into them. | None named |
| analytics | A site monitors how many visitors lack isolation to find broken embeds. | None named |
Risks
- Low tracking value
- Isolation can break embeds
What the platform says
- Google: Making your website cross-origin isolated. web.dev explains the isolation switch that unlocks powerful features like shared memory and precise timers.
Good uses and abuse
Legitimate uses
- Gate APIs
Known abuse
- None meaningful
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 0.1 | Rough identifying entropy, when known |
History
- 2020-07, Chrome 92: SharedArrayBuffer requires crossOriginIsolated
Sources
How well checked: Based on official documentation.