In short
- The checker connects to the provider's server from our machines, exactly as the app would, and reports what the server answers: reachable, account status, expiry, connections allowed, channels, movies, series.
- Three verdicts: online, partial (the server answered but the full analysis ran out of time), error (with the reason: refused, not found, timeout, server error). The score combines ping, content and quality.
- It tests the provider, not your home. A playlist that is online here and dead on your Wi-Fi points to your network or your device, and the guides cover both.
On this page
The checker is the first tool on this site and the first step of almost every troubleshooting guide, so it is worth knowing exactly what it does. It is not magic and it is not a promise: it is a connection to your provider's server, made from our machines, with a structured report of what came back. Here is what each line means, how it is measured, and the honest list of what it cannot tell you.
What you paste
Three kinds of access, detected automatically:
- An M3U link. The checker downloads the playlist and parses it. If the URL turns out to be a
get.phpaddress, it recognizes the Xtream Codes server behind it and runs the fuller Xtream test instead. - Xtream Codes. Server address, username, password. The checker asks the server the same questions the app asks on first launch.
- A MAC portal. Portal URL and MAC address. The checker performs the handshake a box would perform, and reports whether the portal accepts the address.
What you paste is used for that test. A successful test keeps none of your details; an anonymous record of the result (verdict, counts, scores, the server's domain and country) is kept for six months to measure the tool's reliability. A failed or incomplete test also keeps the pasted address, encrypted, so the team can reproduce the failure; it is deleted with the record. Nothing is ever shared.
The verdict
Online. The server answered, the account is recognized, the catalog was read. Everything below is filled in.
Partial. The server answered but not fast enough for the full analysis to complete within the time budget. What you see is what arrived in time; the rest is blank rather than guessed. A partial result at peak hour on a provider that is online at 15:00 is the signature of a server under load.
Error, with a reason. Login refused, address not found, timeout, server error. The reason is the useful part: each one sends you to a different fix, and the login guide and the 8-step diagnosis are organized around them.
A small playlist triggers a notice of its own: with only a handful of items, the content analysis is not representative, and the checker says so rather than draw conclusions from five channels.
The account, from the server's own words
With Xtream Codes and MAC portals, the server describes your subscription, and the checker relays it as is:
- Status: active, expired, disabled, or banned. This is the server's verdict, not ours. Expired and banned look identical in an app (nothing loads); here they are separate lines, and they call for different conversations with the provider.
- Expiry date. The single most useful number on the page. IPTV Guard's monitoring uses it to warn you a week, three days and a day before.
- Connections allowed. How many streams can play at the same time. "1" means the whole household shares one; the connection limit guide explains what that does to a Saturday night.
- Account type (trial or not), creation date, and the output formats the server offers.
An M3U file carries none of this. That is the main reason to prefer Xtream when you have the choice, as M3U versus Xtream Codes explains.
The server
Response time and ping quality: how fast the server answered our first request. Slow does not mean broken, but a server that takes seconds to answer a simple question will struggle with a thousand viewers.
Location, protocol, time zone: where the server appears to be, whether it speaks http or https, and the time zone it declares, which matters for the guide.
Redirects: some providers bounce the request to a second server, sometimes on an unusual port. The checker follows the chain and shows how many hops it took. This is the detail that explains why a playlist works on Wi-Fi and not on 5G: a mobile network may refuse the second hop.
The content
Counts: channels, movies, series, as the server reports them. Consistent with what the provider promised, or not.
Content analysis: the languages and genres present, the share of channels in SD, HD, FHD and 4K, how many carry a program guide (EPG coverage), whether premium formats are offered, how recently the catalog was updated (today, this week, this month, or not in a while). A catalog that has not moved in a quarter says something about the provider.
TMDB enrichment: the share of movies and series whose titles can be matched to the public movie database, which is what gives the app its posters and synopses. A low share means messy naming on the provider's side.
Stream health
This is the line people ask about most. The checker cannot play ten thousand channels in thirty seconds. It picks a random sample of stream URLs, asks each whether it responds, and reports the share that did, as a percentage. It is a temperature reading: 90% means the server is serving; 40% at 21:00 and 90% at 15:00 means the server is saturating at peak; 0% with an online account means the account is fine and the streams are not, which happens when a provider's playlist is stale.
It is a sample, not an inventory. A specific channel can be dead while the health reads 95%, and the guide on black screens covers what to do about one channel.
The score
Three parts, each on its own scale: ping (how fast the server answers), content (how much and how fresh), quality (the share of HD and above, the EPG coverage, the enrichment). It is a summary for a glance, not a judgment: a provider with an excellent server and a small catalog scores differently from one with a huge catalog on a slow server, and both can be exactly what you want.
What no online checker can see
Being honest about the limits is the point of this page.
- Your network. The test runs from our machines. A server that is online here and unreachable from your living room points to your router, your operator, or a block, and the 4G versus Wi-Fi guide is the next step.
- Your device. A stream can respond perfectly and stay black on a box that cannot decode its codec. The H.264 versus HEVC guide explains.
- Who else is watching. The checker sees connections allowed, not connections in use. A slot taken by another device in the house shows up as a cut at playback time, and the app's player tells you then.
- Tonight. A result is a snapshot. Servers change by the hour; the same test at another time is often the most informative thing you can do.
- Legality. The checker reports what a server answers. It cannot know what rights the operator of that server holds, and it does not pretend to. Our guide on what IPTV is sets out where that line sits.
How to use it well
Test before you set up, so a typo does not get blamed on the subscription. Test when something stops working, before touching the app. Test at the hour it fails, then at a calm hour, to separate the provider's load from everything else. And read the verdict's reason before the score: the reason is what tells you what to do next.
In IPTV Guard
The same checks run inside IPTV Guard when you add a playlist and every time the monitoring looks at it: account recognized, expiry known, server reachable. The site's checker is the same engine, free, without an account, for a playlist you have not added yet, or for one that stopped working and you want to know why in thirty seconds.
Frequently asked questions
Does the checker store my playlist or my login?
For a successful test, no: the details are used and not kept. What is kept, for six months, is an anonymous record of the result (verdict, counts, scores, the server's domain and country), to measure the tool's reliability. For a failed or incomplete test, the address you pasted is kept encrypted so the team can reproduce the failure, and it is deleted with that record. Nothing is shared with anyone.
Why does it say online while my app shows nothing?
Because it tests from outside your home. If the server is reachable here and not at yours, the cause is between your router and the server, or in your device: see the guides on 'works on mobile data but not on Wi-Fi' and on black screens.
Why does it say partial?
The server answered but was too slow for the full analysis to finish within the time budget. The numbers shown are what came back in time. Run it again at a calmer hour: a partial at 21:00 and an online at 15:00 is a provider under load.
Can it test every channel?
No checker can, in thirty seconds, on a playlist of ten thousand channels. It tests a random sample of streams and reports the share that responded, as a health percentage. It is a temperature reading, not an inventory.
Does it work with a MAC portal?
Yes. Paste the portal URL and the MAC address the provider gave you. The checker does the same handshake a box would, and reports whether the portal accepts it.
Related guides
- FixMy IPTV Stopped Working: The 8-Step Diagnosis4 min read
- FixLogin Refused, 'Failed to Authorize', No Channels at All: The 7 Causes, From the Silliest to the Most Serious6 min read
- FixWorks on Mobile Data but Not on Wi-Fi: What Happens Between Your Router and the Server4 min read
- UnderstandM3U vs Xtream Codes: What Is the Difference, and Which One to Use5 min read
