We tested 24 slot providers from Malaysia and the answer kept changing

Four providers, Pragmatic Play, JILI, Spadegaming and Playtech, resolve from this connection to 175.139.142.25. That is a single Malaysian address, and it is not a server any of those four companies operate. Requests to it simply hang and time out.

That much matches what is widely assumed about this market. The part that does not is the timing. In a sweep of all 24 providers run at one point in the afternoon, every one of those four resolved to its real address and loaded normally. Pragmatic Play's game pages returned in under two seconds. Forty minutes later, three consecutive rounds one minute apart put all four back on 175.139.142.25 with no response at all.

Nothing was changed on this end between those measurements. Same machine, same connection, same commands.

Two mechanisms, and they are not the same thing

Grouping everything as "blocked" hides a distinction that matters:

• Network-level DNS redirection. Four providers. Your device asks where the site lives and is handed a local address that is not theirs. The provider is not involved and probably does not know. This is the intermittent one.
• Provider-level region blocking. One provider, PG Soft. Its domain resolves correctly to its real servers, and those servers answer with 403 Forbidden, denied by region block. That is the provider or its CDN refusing Malaysian traffic. It was stable across every check.

Same symptom from a player's chair, opposite causes. One is your network deciding what you may reach. The other is the company deciding it does not want you.

What follows for every RTP figure you read

• Anyone can check, but not reliably. A writer who tried Pragmatic Play during the window when it loaded would have read the real figures. One who tried forty minutes later would have concluded the site was down. Neither would know the other existed.
• Intermittent access is worse than a permanent block for accuracy. A permanent block is at least honest about itself. Intermittent access produces some writers who verified, some who copied, and no way to tell them apart afterwards.
• Test before you conclude, more than once. That is the actual lesson here, and it applies to this page too, which is why the number of separate checks is published in its own column.

This applies to our own work. Our RTP table covers Pragmatic Play only, and the figures in it were read during a window when the site answered. They are quoted with their source links so anyone can retry, and if the site does not load when you try, that is now a documented condition rather than a mystery.

Do not take this table on trust. It takes about a minute to reproduce, and the result is specific to your own network.

1. On Windows open Command Prompt, on macOS open Terminal.
2. Type nslookup pragmaticplay.com and press enter.
3. Read the address in the answer section, then paste it below.

1. Each provider's hostname was resolved twice: once through the connection's own resolver, and once through a public DNS-over-HTTPS resolver that the local network cannot rewrite.
2. A mismatch between the two, where the local answer is 175.139.142.25, is recorded as DNS redirected.
3. Each site was then requested over HTTPS with a normal desktop browser user agent. Status codes, response bodies and any block messages were recorded.
4. For the reachable providers, a games or product listing page was requested and the served HTML searched for an RTP percentage, a volatility rating and a maximum win figure.
5. Pragmatic Play was additionally read at the individual game page level, which is where its per-game RTP appears.
6. Eight hosts were then re-checked three more times at roughly one minute apart, after an earlier full sweep, to see whether a single reading could be trusted. It could not.

Limits worth stating

• One connection, one date, several rounds. Results are from a single Malaysian residential connection on 3 September 2026. Eight hosts were checked four times, the other sixteen once. Another ISP may resolve differently, and this page is itself the evidence that filtering changes within the hour.
• Plain requests do not run JavaScript. A provider rendering its specifications client-side would show as "not in the HTML" here while publishing them perfectly well to a browser.
• Reachable is not the same as complete. Most reachable providers served listing pages with no RTP in the markup. That is a finding about those pages under a plain request, not a verdict on what the providers publish.
• This page makes no claim about why any site is unreachable, or about who applied any filtering.

Why can I not open pragmaticplay.com in Malaysia?

Usually because the address your device is given is not the real one. On this connection pragmaticplay.com often resolves to 175.139.142.25, a Malaysian address Pragmatic Play does not operate, and the request then times out. But not always: in one sweep it resolved correctly and its game pages loaded in under two seconds, then forty minutes later it was redirected again. The same intermittent pattern was observed for JILI, Spadegaming and Playtech.

Does that mean the provider's website is down?

No. Resolving to the wrong address and being offline look identical from a browser, which is the confusing part. Checking the same hostname through a public DNS resolver returns a different, working address, which is how the two cases can be told apart.

Which slot providers publish their RTP publicly?

Of the 24 tested, two were found with an RTP percentage in the HTML served to a plain request: Pragmatic Play at 96.50% on an individual game page, and Fa Chai Gaming at 96.5% on its games listing. Most others returned pages with no RTP in the markup, which frequently means the specifications are rendered by JavaScript rather than that nothing is published. Five could not be read at all at the time of checking.

So where do Malaysian sites get their RTP numbers?

From each other, for the most part. If a provider's site cannot be opened from Malaysia, the person writing a Malaysian page about that provider's games did not read it there either. That does not make every figure wrong, but it does mean the numbers travel without a way to be checked against the source, so an error entering the chain has nothing to correct it.

How do I check this myself?

Run nslookup on the hostname from Command Prompt or Terminal and read the address returned. If it is 175.139.142.25 for a foreign company's domain, you are being given a local address that is not theirs. The checker on this page compares whatever you paste against that address.

Is this page saying the filtering is wrong?

No. It takes no position on whether any filtering is appropriate or who applied it, and it does not claim to know who applied it. It documents two things that can be measured: that four provider domains are redirected to an address that is not theirs, and that the redirection comes and goes within the same hour on the same connection.

What this test makes possible, and what it makes impossible, is worked through on two other pages.

The figures that could be read

47 Pragmatic Play RTPs, each with the source link it was read from, collected during a window when that site answered.

The same problem one layer down

If the provider's site cannot be reached, neither can the reference values that would let you verify an installer. Eight checks that work without them.

What a provider actually publishes when you can read it

Provider-stated RTP and feature text for four titles, quoted with sources, and one entry left blank for the provider that blocks Malaysia.

OPEN A U88 ACCOUNT

Disclosure: this site is run by a U88 affiliate and earns a commission on accounts opened through the link above. That is relevant to a page arguing you should verify claims rather than accept them, so treat this page the same way: the test is described in enough detail to be repeated, and everything here can be checked without us. U88's minimum deposit is RM30. 18+.