All relays

moq.dev CDN

moq.dev

cdn.moq.dev:443/anon

QUIC WT drafts 14–20 IPv4 IPv6

A deployment of moq.dev. Everything below was measured on this deployment, at whatever version and configuration it was running — it is not a measurement of that codebase. About this endpoint

At a glance

Identifies itself as
moq-lite-rs — under 0x07, which draft 14 does not define
Protocols accepted
moqt-20, h3, moqt-19, moqt-18, moqt-17, moqt-16, moqt-15
Media delivery
not attempted
Violations recorded
1

Certificate

Subject
CN=cdn.moq.pro
Issuer
C=US, O=Let's Encrypt, CN=YE1
Valid until
2026-12-12 89 days left
Trust
publicly-trusted
Verification
Completed with the certificate verified

Control messages

Which control messages this endpoint answered, per draft. An error reply is still an answer — ok and err are both support; what is recorded as missing is a message that got no answer at all. A dash is neither: it means the exchange ended on our side, so nothing about this endpoint was measured there.

Draft SUBSCRIBEFETCHTRACK_STATUSSUBSCRIBE_NAMESPACEPUBLISH_NAMESPACE
20 QUIC
19 QUIC
18 QUIC
17 QUIC
16 QUIC
15 QUIC
14 WT

Specification violations

namespace-tuple-size draft 14 over WebTransport, during messages/subscribe

codec error: namespace tuple size 0 is not allowed here (max 32)

What the specification requires

Section 2.4.1: "Track Namespace is an ordered N-tuple of bytes where N can be between 1 and 32. … If an endpoint receives a Track Namespace tuple with an N of 0 or more than 32, it MUST close the session with a Protocol Violation." SUBSCRIBE_NAMESPACE repeats it of the Track Namespace Prefix. Draft-07 states the range without the consequence; drafts 17 and later lower the floor to 0.

Setup parameters

What this endpoint sent back in its setup response, per draft. A parameter with no name is a code point the negotiated draft does not define.

draft 14 · WT

  • 0x40b5a not defined by this draft = 1
  • 0x02 max_request_id = 4294967295
  • 0x07 not defined by this draft = moq-lite-rs (moqt_implementation in 15–20)

Is this your relay?

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.