IPTV test

Checks URL accessibility, HTTP response, and obvious format/access problems. HTTP 200 does not guarantee every stream plays.

What this check examines

HTTP status of the playlist URL, following redirects to the final address (redirect targets are re-validated, not trusted blindly).
Content type and body shape: whether the response looks like playlist text or HTML. An HTML body on a playlist URL is the classic wrong-link signal.
M3U header presence — the file must open with #EXTM3U.
Entry and error counts from parsing (up to the first 8 parse errors shown), plus bytes fetched and check duration.
Content breakdown: group distribution (top 10) and sample entry names, so a healthy verdict comes with visible proof of what is inside.

Reading the verdict

Non-200 status: access or hosting fault. Fix the URL or the access; no player setting bypasses it.
HTML instead of playlist content: wrong link (webpage, login wall, expired share). Get the direct file URL.
Missing header: not a valid M3U response, even at HTTP 200.
Zero entries: effectively empty list. See empty playlist diagnosis.
Reachable and parsing: the list is healthy at this moment. Individual streams remain unchecked — playlist health and stream health are separate questions.

What this check cannot tell you

Whether individual streams play — it never opens channel URLs.
Geo-restriction or per-network blocking — a URL healthy here can fail on another network.
The future — token-rotated sources invalidate results within hours. Re-test, don't screenshot.

FAQ

The test passes but my player shows nothing. Why? Stale cached import, wrong input mode (M3U vs Xtream), or filters hiding everything. The full order is in M3U not working?

Why did it time out? The host is slow, down, or blocking this network. Retry once, then test from another network to separate server faults from local blocks.

Is the tested URL stored or published? No. Test inputs are processed per request and never appear on public pages.

Can I test URLs with tokens or embedded logins? Token-bearing query strings test normally. URLs with embedded username:password credentials are rejected outright — strip credentials and test the clean URL, or use the Xtream test for login-based access.

Method and limits

Methodology: server-side fetch with a 12-second timeout and 5 MB cap, http(s) only, private and metadata hosts blocked, redirect targets re-checked, rate-limited to 10 checks per minute per client. Results describe the observed response at the shown timestamp.

Sources

M3U diagnosis order this check is built for.
Playlist directory for URLs worth testing.