Provides a mechanism for a server to specify a new origin for a page to run in that is named and contained within the same physical (scheme/host/port) origin. For example, an application running at which the server places in the Suborigin namespace Foo will run in a new origin based on the tuple (https,, 443, Foo). This would be considered a different origin space from (https,, 443) or (https,, 443, Bar)



Specification link

Specification being incubated in a Community Group

Status in Chromium


No active development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • Mixed signals


Last updated on 2020-11-14