Submit form
Email + optional token
CHROME EMAIL VERIFICATION PROTOCOL · EXPERIMENT 01
Less friction.
Same trust boundary.
Build the form. Follow the token.
See exactly where your email fallback belongs.
FORM ANATOMY
Start with the essentials.
A session-bound nonce connects the browser token to your server. Replace the placeholder before shipping.
YOUR SIGNUP FORM / VISUAL PREVIEW
Create your account
One small form. Two verification paths.
◈
Preview only · no account is createdHidden verification tokenFilled by the browser when available
signup.html
Illustrative markup. Server verification, nonce generation and email delivery are yours to implement.
A BRANCHING WALKTHROUGH
What comes back with the form?
Verify the token
Signature, audience, expiry & session nonce
Continue verification
This is a model of your application’s decision, not a live EVP test. Browser availability and origin-trial state still need a real check.
Need a separate browser profile? Open WebTraceCheck ↗. Confirm the actual browser version and EVP availability yourself.
STATIC MARKUP INSPECTION
Bring your own form.
Issuer metadata / optional
Static checks only. No signature, DNS or delivery validation.
No uploads. No saved form content.
The empty-token path matters just as much as the happy path. Use a CleanTempMail test inbox to exercise ordinary confirmation emails on your own application.
WebTraceCheck and CleanTempMail share this site’s operator. No EVP issuer support is claimed for either service. Use non-sensitive test accounts; separate service limits apply.