English guide
Stream diagnostics: why will this channel not play?
Guessing costs hours. This tool sends a real HTTP request to a stream address and shows the answer: status code, response time, content type and size, CORS header, Range support and any redirect. It measures instead of speculating — and it is the first place to look when a channel works for a friend but not for you.
Open stream diagnostics →1. Enter the addresses
up to 5 addressesHow to read a diagnosis
1. Paste one to five addresses
Five per run is the limit, and that is deliberate: this tool is for understanding one problem stream, not for scanning a catalogue. For hundreds of channels use the M3U checker, which batches, retries and reports.
2. Read the status and content type together
A healthy live stream answers 200 with a media type such as video/mp2t, or application/vnd.apple.mpegurl for HLS. A 200 with text/html is the classic trap: the panel returned a login or error page, and the player shows a black screen.
3. Check the CORS header
Browser-based players need Access-Control-Allow-Origin. Without it a stream can play fine in VLC or TiviMate and still fail in a web player — the result flags that case separately instead of blaming the stream.
4. Look at Range and redirects
Range support enables seeking and lets us probe only the first 512 bytes. A redirect chain explains slow starts, and a redirect to another host often means the token or IP was rejected at the second hop.
5. Compare with a desktop player
Open the same URL in VLC or TiviMate. If it plays there but not in the browser, the problem is CORS or mixed content (HTTPS page loading an HTTP stream), not the stream itself.
What the answers mean
- • 200 + video/mp2t or mpegurl — The server is delivering media (or a manifest). This is what a working channel looks like.
- • 200 + text/html — A login or error page came back instead of video — the most common cause of a black screen.
- • 403 — Usually an IP or user-agent block. Try another network, or ask the provider to whitelist you.
- • 404 — The stream path changed; download a fresh playlist instead of editing the old one.
- • No CORS header — Fine for VLC, broken for a browser player. Not the provider’s fault, but it decides where you can watch.
What this test cannot tell you
The request comes from our worker, not from your connection: a panel that allows your home IP but blocks datacenters can answer differently here than it will for you. The test also says nothing about video quality or long-term stability — a 200 right now is a snapshot. And five addresses per run is a hard limit by design; bulk health checks belong to the M3U checker.
FAQ
Where do I start when a channel shows a black screen?+
In this order: is the content type HTML instead of media, is the CORS header missing, is there a redirect to another host, and — for HLS — do the segments return 403/404? Those four answers cover almost every case.
Can I diagnose a hundred channels at once?+
No, five per run. For volume use the M3U checker: it tests in batches, retries timeouts and produces a CSV report plus a clean playlist.
Why does Range support matter?+
It lets us read only the first bytes instead of pulling a whole file, and it enables seeking in players. A server without Range forces full downloads, which is why some of our probes fall back to headers only.
Are the addresses or results stored?+
No. Addresses are used for the request and the result is rendered in your tab. There is no log and no database.
Related guides · Speed test · M3U checker · Türkçe