← back to v150 · email-verification-protocol
conformance · v150
v150 · email-verification-protocol — conformance probe
8 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
8
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
email-input-autocomplete-email |
EVP starts from an email input that advertises autocomplete=email. spec ↗ | script | … | |
email-input-nonce-roundtrip |
The relying-party page can bind a session nonce to the email input. spec ↗ | script | … | |
native-evp-event-detectable |
The browser exposes a detectable native EVP event surface for receiving an email verification presentation token. spec ↗ | script | … | |
secure-context-readable |
The page can determine whether the current context is secure before attempting native EVP. | script | … | |
demo-sample-route-returns-jwt |
The local demo backend returns a compact signed token for an email, audience, and nonce. spec ↗ | script | … | |
demo-token-payload-carries-email |
The local demo token includes the email address that was requested. spec ↗ | script | … | |
demo-validator-accepts-fresh-token |
The local backend accepts a fresh signed token when audience and nonce match. spec ↗ | script | … | |
demo-validator-rejects-replay |
The local backend rejects the same nonce when a token is validated twice. spec ↗ | script | … |