moq.dev CDN
cdn.moq.dev:443/anon
The moq.dev project's own public relay, published as reachable over WebTransport, raw QUIC and WebSocket.
What this is
What TestLab measured
What this endpoint answered on 2026-09-14. One sweep, on one occasion — not a claim about availability, and not a grade.
- Transports answered
- QUIC and WebTransport
- Drafts answered
- drafts 14–20
- Identifies itself as
- did not say
- Media delivery
- not attempted
- Violations recorded
- 1
- Address families
- IPv4, IPv6
One reply left the specification
- namespace-tuple-size draft 14 over WebTransport
What each one is, and what the specification requires, is on the report.
Certificate, per-draft control message support, the delivery run and every recorded violation in full.
The moq.dev project’s own public relay, maintained and published as reachable over three transports: WebTransport, raw QUIC and WebSocket. The TestLab probe speaks the first two and does not test WebSocket.
The cdn. label in the hostname is chosen by whoever registered the name and is not evidence about the deployment behind it.
This endpoint names itself under a code point the negotiated draft does not define: it sends draft-15’s implementation parameter on draft-14. “Did not say” would be wrong about it — it did say, just not somewhere that draft told the probe to look.
Elsewhere running moq.dev
One other endpoint runs the same implementation. Each is a separate deployment at its own version and configuration, so what one answers is not a claim about the others. All of them are run by the same operator as this one.
Is this your endpoint?
If something here is wrong, tell us — we keep what each result rests on, so a disputed one gets re-read rather than re-argued. We can also run this against endpoints that are not public.