As of November 10, 2026, Google had opened a Chrome Origin Trial for the proposed Email Verification API. The WICG proposal would let a website confirm that a visitor controls an email address without sending a one-time code or magic link. The trial starts with desktop Chrome 150, and Gmail is the first participating email provider.
The proposed process puts the browser between the website requesting verification and the email provider issuing it. If the visitor is already signed in to the provider, the browser can obtain a signed token in the background and add it to the website’s form. The website’s server checks the token when the form is submitted. Google says the provider cannot tell which website initiated the request.
For developers, the form needs an autocomplete hint on the email field and a hidden field carrying a session-bound nonce. The server must verify the token’s signature using the provider’s key. Resend’s Phil Nash has published a walkthrough, an npm package and a Next.js example for parsing and verifying tokens.
The proposal has drawn mixed reactions. Some Hacker News commenters welcomed a way to avoid switching to an inbox, particularly when confirmation messages are delayed or filtered. Others questioned the privacy benefit: one argued that a website may reveal itself to the provider later by sending welcome or reminder emails. Another viewed the provider’s inability to identify the requesting website as a drawback. Developers who use a different address or alias for each site also noted that verification must fall back to email when a provider cannot confirm an alias.
That fallback remains necessary more broadly. If a visitor is not signed in to Gmail in Chrome, a site can still send a conventional confirmation email. Existing syntax, MX and SMTP checks can continue to cover addresses the API cannot handle.
An October 2026 Chrome update described an Android and third-party Origin Trial for Chrome 154, a change to the Sec-Fetch-Dest issuer value to email-verification, and a Chrome 156 change to return email addresses as users entered them. Because the API remains experimental, sites testing it should track protocol changes and treat it as an optional enhancement rather than a replacement for existing verification methods.



