BUSMAIL — ORIGINAL APPLICATION ACCEPTANCE CASES
These are test specifications, not tokens, verification code or execution results.
Use an application and disposable test identities you control.

1. EMPTY TOKEN: normal verification route; never infer verified=true.
2. MALFORMED PACKAGE: verification fails; application follows documented fallback.
3. EXPIRED TOKEN: must not establish current email verification.
4. WRONG NONCE: must not verify another active session.
5. WRONG AUDIENCE: must not verify a different relying origin.
6. EMAIL MISMATCH: must not verify the submitted different address.
7. SIGNATURE / KEY-BINDING FAILURE: decoded claims are not trusted evidence.
8. FULLY VERIFIED PACKAGE: email result may proceed; admission and session still tested.

BLANK RESULT
Case number:
App release:
Browser/version and participating-provider state:
Trial state actually checked:
Expected application decision:
Observed server decision:
Fallback receipt observation if relevant:
Resulting session observation:
Unresolved question:

No raw tokens, nonces, keys, passwords or recovery links in shared reports.
Source: https://developer.chrome.com/docs/identity/email-verification/verifier