twang. SIGNAL CONNECTION LAB POC 01 Signal TLS proxy notes

A SIGNAL, THROUGH THE WEB

Give the connection
a little twang.

Find out what makes it through. Probe Signal’s endpoints directly using native browser HTTPS and WebSockets. No backend or relay.

Checking contextChecking browser APIsChecking networkNo account or message keys required
01

Set up a probe

Use the browser’s own networking. A failed probe may reflect certificate trust, CORS, or server policy.

Requests the endpoint root. Any readable HTTP status proves that an HTTP response arrived.

Signal endpoints HTTPS / WSS

Bounded, unauthenticated checks. Nothing is sent until you run a probe.

02

Read the signal

Ready

Your connection results will appear here.

Waiting for a vibration.

Choose your endpoints and run a probe.
Each result includes timing and the evidence behind it.

Browser· · ·Signal
EVENT LOG0 events

No network activity yet.

↗

A response is a response.

401, 403, and 404 can still prove a working transport. They don’t mean a Signal account is authenticated.

⌁

A browser error is ambiguous.

Browser APIs usually hide TLS and handshake details. We report what was observed, without guessing the cause.

◇

Know the browser boundary.

Static pages cannot open raw TCP sockets or run an independent TLS handshake. Certificate trust is controlled by your browser.

Certificate trust & diagnostic scope

Native HTTPS and WSS use the browser’s certificate validation. This app cannot add Signal trust roots, bypass CORS, or speak raw Signal TLS proxy protocol.

WebSocket tests stop after an upgrade; they do not decode provisioning messages. They never generate a linking QR code, link a device, register an account, or request a user’s messages. Results live in this tab until you clear them or export a local report.