Cloudflare draft-16
Cloudflaredraft-16.cloudflare.mediaoverquic.com:443
A deployment of moq-rs, operated by Cloudflare. 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
- did not say
- Protocols accepted
- moqt-16, h3
- Media delivery
- not attempted
- Violations recorded
- none
Certificate
- Subject
- CN=*.cloudflare.mediaoverquic.com
- Issuer
- C=US, O=Let's Encrypt, CN=YE2
- Valid until
- 2026-10-04 20 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 | SUBSCRIBE | FETCH | TRACK_STATUS | SUBSCRIBE_NAMESPACE | PUBLISH_NAMESPACE |
|---|---|---|---|---|---|
| 16 QUIC | ✗ | ✗ | ✗ | ✗ | ✗ |
| 15 WT | ✗ | ✗ | ✗ | ✗ | ✗ |
Specification violations
None recorded. Nothing this endpoint sent broke a requirement the probe checks — which is not the same as saying it implements the draft completely.
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 16 · QUIC
- 0x02 max_request_id = 100
draft 15 · WT
- 0x02 max_request_id = 100
Notes
- — the peer is up but refused the offered protocols on at least one transport
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.