Chrome Email Verification: check the trial changes and fallback

Identify your role before changing the flow

This update is useful for developers maintaining email verification. The browser mediates between a verifier site and an issuer. The WICG specification is still a draft, not a W3C Standard. The official overview describes an origin trial, so keep the existing email-confirmation path available.

Merewood’s post calls out optional kid handling during signature verification, the hyphenated Sec-Fetch-Dest: email-verification value, and preserving the submitted email value in issuer responses. Verifiers and issuers have different responsibilities; use the corresponding official guide rather than copying a browser-only example.

Keep failure and delivery separate

The overview says missing or invalid verification tokens should fall back to the existing confirmation flow. Proving control of an address does not prove that a welcome email was delivered. Boloop has not run the trial; this is an attributed reading recommendation, not a tested integration.