Provider-neutral self-test pilot
Hola describes its free service as a peer-to-peer network in which members use the network and contribute to it, with idle resources shared for the benefit of the whole. Its paid tier is described differently, as running on a dedicated network of servers so that your device is not used as a node. That distinction is unusually visible in a leak test, because the two arrangements tend to produce quite different looking exit addresses.
Live test
On Hola the exit address is worth reading closely: the free service is described as peer-to-peer, so the address may belong to a residential connection rather than a datacentre.
Current-session checks
Take a reading before and after connecting, and note which tier you are on. Hola documents the free and paid services as working differently, and the exit address is where that shows.
Before you read the result
The points below come from Hola's own frequently asked questions and help centre articles about how its network operates.
Hola states that it works because it is a peer-to-peer network in which you use the network and contribute to it, and that free use is in return for contributing idle resources. An exit address that resolves to a residential connection rather than a hosting company is consistent with that description rather than a sign of misconfiguration.
Hola says its premium service lets you use Hola without your resources being used as a network node, and describes it as running on a dedicated network of high performance servers. Which tier you are on therefore changes what a lookup on your exit address should be expected to return.
The company describes using a small fraction of a member's computer resources while they are not in use, for the benefit of the network. That is a statement about the free service as a whole. It is not something a page in the browser can observe or confirm for your particular device.
A network assembled from members is not a fixed list of machines in the way a server fleet is. Two readings taken on different days can therefore differ more than they would elsewhere, and a difference on its own is weaker evidence here than it would be with a provider running its own hardware. If you are trying to establish whether something changed in your own setup, take both readings in the same sitting rather than comparing today against a note you made last week.
Whatever tier is in use, the checks below describe one browser in one session: the address presented, the resolver that answered, what WebRTC produced. They do not describe the network arrangement behind the address, and no reading here should be treated as confirming or refuting it.
Between the readings
The address visible during a Hola VPN session can change without you touching anything. Recording a disconnect is how you watch it move, rather than catching one position of it by chance.
Safe Copy exports use safe summary categories and remove raw IP, exact city, full user-agent, raw fingerprint data, raw resolver IPs and WebRTC candidates. It is not a certificate, provider audit, or proof of anonymity.
FAQ
Hola describes its free service as a peer-to-peer network in which members contribute idle resources. An address belonging to a home connection rather than a hosting company is consistent with that description.
Hola says the premium service lets you use it without your resources being used as a network node, and describes premium as running on a dedicated network of servers rather than on members' devices.
Hola states that free use is in return for contributing idle resources, and describes using a small fraction of a member's computer when it is not in use. A browser check cannot verify that for your device.
A network assembled from members is less fixed than a server fleet, so more variation between sessions is expected. On its own a change is weaker evidence here than it would be with a dedicated network.
No. MyIPScan does not turn these checks into rankings or recommendations. Every provider page states what that provider documents and reports what your own browser exposed.
What this browser presented in this session: the address, the resolver, the WebRTC candidates and the IPv6 line. Conclusions about the network arrangement behind them need sources outside a browser.