Skip to Content
Platform.Ontology

Secure context and cross-origin isolation

Flags telling whether the page is HTTPS and isolated from other origins.

Gets silentlyDevice detailsBrowser stateWeb browsersWhen the page loadsWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported472015-12-01None
EdgeSupported792020-01-15None
FirefoxSupported492016-09-20None
SafariSupported11.12018-04-12None
Safari on iPhoneSupported11.32018-03-29None
Chrome on AndroidSupported472015-12-02None
Samsung InternetSupported5.02016-12-15None

How a site asks for it

APIwindow.isSecureContext, window.crossOriginIsolated
Browser compat keysapi.Window.isSecureContext
api.Window.crossOriginIsolated
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnone needed (no grant)
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: object
How often: static per session

FieldTypeUnitRangePrecision
isSecureContextbooleanNonetrue or falseNot listed
crossOriginIsolatedbooleanNonetrue when COOP+COEP setNot 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

TypeExampleApps
gamesA browser game engine needs isolation to use shared memory threads, so it runs at a smooth frame rate.Unity WebGL games
creativeA browser video editor needs it to run fast video code in the page.Clipchamp
developerA web code editor runs a full programming environment in the tab, which needs the isolation flag.StackBlitz
productivityA browser version of a design app turns on advanced timers and threads for heavy files.Figma
securityA bank locks down its pages so another site cannot peek into them.None named
analyticsA 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

Good uses and abuse

Legitimate uses

  • Gate APIs

Known abuse

  • None meaningful

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits0.1Rough identifying entropy, when known

History

  • 2020-07, Chrome 92: SharedArrayBuffer requires crossOriginIsolated

Sources

How well checked: Based on official documentation.

On this page