- The Email Verification API enables browsers to verify email ownership directly with providers, bypassing disruptive OTP or magic link methods.
- Key parties include the Verifier (site collecting email), Email Provider (hosting the address), and Issuer (managing the account session).
- The process leverages autofill, hidden form fields with nonces, DNS records, and JWT tokens to confirm the email without user interruption.
- Validating a verification token involves parsing the token, checking expected values, verifying key binding and DNS records, and confirming the issuer's signature.
- Implementing verifiers requires specific HTML form attributes, while providers need to expose DNS and .well-known endpoints and integrate with FedCM and Login Status APIs.
- The API is a progressive enhancement, falling back to traditional email verification if the browser doesn't support EVP or validation fails.
- Participation requires signing up for the Chrome origin trial, with fine-grained control via token inclusion, and feedback can be reported via specified GitHub repositories.