Step 1
Confirm your test details
This creates the participation record used to review evidence later.
Nodex
Beta
Validation suite
Private beta access
Use your invitation once, follow a guided checklist, and send the test evidence without opening developer tools.
Signed in as tester
Follow the checklist below. We will collect the browser diagnostics and keep a clear record of your participation.
Before you start
Test type
Choose the simplest option that matches your situation. Multi-person tests wait until the right people are online.
Connectivity check
The test unlocks once everyone needed is showing as online. This refreshes automatically every 30 seconds.
Checking presence...
Step 1
This creates the participation record used to review evidence later.
Step 2
This checks browser cache behavior, encrypted responses, and the diagnostics needed for review.
Step 3
Choose what happened. If you are unsure, choose partial and add a short note.
Local log bundle
The bundle includes simulation events, browser details, storage estimate, and your selected result.
Hacker POV
Every peer-to-peer payload is opaque ciphertext. The IV and auth tag make replay, tampering, and key-mismatch attacks detectable at decrypt time.
—
—
—
—
—
AES-GCM-256 — the auth tag rejects any tamper or key mismatch. Without the session key an attacker only observes random bytes.
Admin lab
Visible only for admin tokens. Use this to coordinate non-technical testers without sharing internal tooling.
Epidemic control
Token management
Wire captures
Every encrypted response logged by the API — shows what any network observer would see.
No captures yet. Run a real test first.
Monitor
Security audit