Can I use
?

Signed HTTP Exchanges (SXG)

- OTHER

Part of the Web Packaging spec, Signed HTTP Exchanges allow a different origin server to provide a resource, and this will be treated as if it came from the original server. This can be used with AMP CDNs, for example, to allow the original URL to be displayed in the URL bar.

Chrome

  1. 4 - 70: Not supported
  2. 71 - 72: Partial support
  3. 73 - 116: Supported
  4. 117: Supported
  5. 118 - 120: Supported

Edge

  1. 12 - 18: Not supported
  2. 79 - 116: Supported
  3. 117: Supported

Safari

  1. 3.1 - 16.6: Not supported
  2. 17.0: Not supported
  3. 17.1 - TP: Not supported

Firefox

  1. 2 - 116: Not supported
  2. 117: Not supported
  3. 118 - 120: Not supported

Opera

  1. 9 - 63: Not supported
  2. 64 - 101: Supported
  3. 102: Supported

IE

  1. 5.5 - 10: Not supported
  2. 11: Not supported

Chrome for Android

  1. 117: Supported

Safari on iOS

  1. 3.2 - 16.6: Not supported
  2. 17.0: Not supported
  3. 17.1: Not supported

Samsung Internet

  1. 4 - 10.1: Not supported
  2. 11.1 - 21: Supported
  3. 22: Supported

Opera Mini

  1. all: Not supported

Opera Mobile

  1. 10 - 12.1: Not supported
  2. 73: Supported

UC Browser for Android

  1. 15.5: Supported

Android Browser

  1. 2.1 - 4.4.4: Not supported
  2. 117: Supported

Firefox for Android

  1. 117: Not supported

QQ Browser

  1. 13.1: Supported

Baidu Browser

  1. 13.18: Supported

KaiOS Browser

  1. 2.5: Not supported
  2. 3: Not supported

Note this requires the page to be delivered signed by a certificate with the CanSignHttpExchanges extension.

Resources:
Developer Preview of better AMP URLs in Google Search
Microsoft Edge Platform Status - Supported
Signed HTTP Exchanges on Google's Web Development site
GitHub home page for Web Packaging
Signed-Exchange: Solving the AMP URLs Display Problem
Mozilla's Position about Signed HTTP Exchanges (harmful)
Chrome platform status - Shipped