Which CDNs serve you
Read from the response headers your CDN already sends —
Via, X-Cache, Server and the
vendor-specific ones.
No account · No credentials
Paste a playback URL. See what you run today.
We fetch the manifest and follow the DNS the same way any viewer's player would. Everything we report comes from what is already public.
- Which CDNs answer for you, and whether more than one already does.
- How the stream is built — ladder, segment length, DRM, tokens.
- Whether anything is measuring your viewers, or routing them blind.
HLS (.m3u8) or DASH (.mpd). We store a SHA-256 hash of the URL for rate-limiting — never the URL itself.
No URL to hand? Read how the routing works first, or see what the report contains.
Requested
We run this check with you, not at you. Paste the URL
and we come back with the report above — read by a person, so
you get the reading of it as well as the numbers.
What comes back
Delivery parameters, measured in real time from your stream.
Every value names its source — DNS, the manifest, or delivery headers. The CMCD check tells you whether anything is measuring your viewers at all.
Who is serving it
Whether you are already multi-CDN
Repeated requests that come back from different providers mean something is already splitting your traffic.
Your CNAME chain
Where delivery is being resolved, and by whom.
How the stream is built
Your bitrate ladder
Renditions, resolutions and codecs, straight from the master manifest.
Segment duration
Which tells us your latency class, and whether you are running low-latency HLS.
DRM and encryption
Which scheme is in use, and whether keys are delivered in a way that survives a CDN switch.
Whether it can be steered
What is doing the splitting
A steering vendor, DNS weights, a list inside your player, or alternates in the manifest itself.
Whether anything measures your viewers
If there is no CMCD, whatever is routing your traffic is routing it blind. This is usually the finding that matters most.
Signed URLs
Whether your tokens would survive a mid-stream move to a different CDN — a common way multi-CDN quietly breaks.
When you want to go further
Four ways to bring your setup across.
You never have to start from an empty form.
1 · From a URL
No credentialsWhat this page does. Works for every provider, because it reads what any player can already see.
2 · From your provider
Read-only accessConnect your CDN or steering vendor with read-only credentials and we read the configuration itself. We never write to your existing provider.
3 · From a file
You send the fileTerraform state, or an exported configuration. If you manage delivery as code, this is usually the fastest route — and we need no access at all.
4 · Together
With usIf your setup is homegrown or your vendor has no export, we walk through it with you and transcribe it. Nothing is a dead end.
Whatever route you take: read-only, always. We import
configuration, never credentials — you re-enter CDN access inside vidNT.
And before anything is created, you see a preview that lists every item
we could not map. Nothing is dropped quietly.
What to do next
Compare first. Move traffic later — if at all.
-
1
On paper
We show what we would have routed differently, and why, against your own measurements. Zero traffic moves.
-
2
In shadow
The decision engine runs live beside your current setup. Real measurement, still zero traffic.
-
3
A canary, if you want one
One percent of real viewers is a separate decision, and it is yours. Reversible in one click.