Provider-neutral self-test pilot
Mozilla VPN is the clearest case on this list of a product whose exit belongs to somebody else. Mozilla states that Mozilla VPN is built on top of Mullvad VPN infrastructure and uses the same servers, and that the connection runs on WireGuard. So the network name attached to your address after connecting will often read Mullvad rather than Mozilla, and that is the documented arrangement rather than a mismatch worth worrying about.
Live test
Expect the network behind your address to name Mullvad rather than Mozilla: Mozilla states the two products use the same servers.
Current-session checks
Read the signals before and after connecting. On Mozilla VPN the line that surprises people is the network name, because the servers are Mullvad's and are documented as such.
Before you read the result
The points below come from Mozilla's own product pages and support articles for Mozilla VPN.
Mozilla says plainly that Mozilla VPN is built on top of Mullvad VPN infrastructure and uses the same servers. A lookup on your address after connecting can therefore name Mullvad, or the hosting company behind a Mullvad site, and still be exactly right. Reading that as evidence of a misconfigured tunnel is the common mistake here.
Mozilla describes the service as running on WireGuard, which it calls one of the most performant VPN protocols. For a reading on this page the protocol matters only indirectly: it decides how the tunnel is built, not which address is presented. What you can check is whether the address changed at all.
Mozilla documents a limit of five simultaneous devices on a subscription. If a device silently fails to connect because the limit was reached, the checks here will report an ordinary connection with no error attached. That is one of the few cases where a plain reading is the first hint that a subscription rather than a setting is in the way.
Because the infrastructure is shared, the network characteristics you can observe from a browser are largely Mullvad's. MyIPScan keeps a separate walkthrough for that provider at the Mullvad self-test, and the two pages describe different products over a common set of exits rather than one product written up twice. Where they differ is in what each company publishes about its own client, and it is the client rather than the server that decides most of what a check like this one can see.
Mozilla's own help pages for the product do not set out IPv6 handling or resolver addresses in the way some providers on this list do, so this page states neither. That gap is worth naming rather than papering over: if your IPv6 line has content, treat it as a question to put to the provider rather than as something settled by anything published here or inferred from the shared infrastructure. A page that guessed would be easier to read and worse to rely on.
Between the readings
The checks on this page sample a Mozilla VPN session once. What happens between a dropped tunnel and a restored one is a sequence, and a sequence needs more than one reading to describe.
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
Because Mozilla states that Mozilla VPN is built on top of Mullvad VPN infrastructure and uses the same servers. A lookup naming Mullvad is the documented arrangement rather than an error.
Mozilla describes the service as running on WireGuard. The protocol decides how the tunnel is negotiated; it does not by itself change which address a website records for you.
Mozilla documents up to five devices on an active subscription. A device that quietly fails to connect at the limit will produce a reading that simply looks like no VPN at all.
Its own help pages for the product do not set out IPv6 handling the way some providers do, so nothing is claimed about it here. Ask the provider before drawing a conclusion from the IPv6 line.
No. They cover two products that share a server list. The Mullvad walkthrough describes that provider's own documented behaviour, which is not automatically what Mozilla publishes for its product.
Whether the address, resolver and WebRTC candidates your browser presented changed between the two readings. Anything about the servers behind them is outside what a browser can observe.