Before You Block VPNs This Black Friday, Look at Where Firefox's Built-In VPN Exits

Before You Block VPNs This Black Friday, Look at Where Firefox's Built-In VPN Exits

On November 10, Mozilla removed the data cap from the free VPN built into Firefox. Until January 31, 2027, anyone signed in to a Mozilla account on desktop or Android, wherever the feature is offered, can send all of their browsing through it. The allowance used to stop at 50 GB a month, and the location picker added in May lets them choose the country they appear to be in. The offer runs through Black Friday (November 27), Cyber Monday (November 30), Christmas and the January sales. Adobe expects $47.5 billion of US online spending in the five days from Thanksgiving to Cyber Monday alone.

A checkout that declines every address flagged as a VPN will spend those weeks refusing people who clicked a toggle in their browser. We went looking for the exits before the rush. We found them in 38 IPv4 /24s, and in 37 IPv6 /44s cut from a single /36, that are registered to Mozilla and announced by Fastly's AS54113, with each /24 placed in one city. One of the blocks is literally called MOZILLA-FIREFOX-VPN. Traffic this easy to recognize can be scored, and we think blocking it is a mistake.

A proxy inside the browser, operated by Fastly

The feature shipped in Firefox 149 on March 24, 2026, as a beta for desktop users in the United States, the United Kingdom, Germany and France. Despite the name it is a proxy, and it only serves the browser. Firefox opens an HTTP CONNECT tunnel to a proxy server (over HTTP/2 in the initial rollout) and loads pages through it, while every other application on the machine keeps its ordinary address. (The paid Mozilla VPN is a separate product that covers the whole device.)

Mozilla names the operator. Its feature page says traffic is "routed through a proxy server powered by Fastly", and Fastly wrote on June 15: "That proxy is ours." According to that post the proxy "only knows the destination hostname and port", Fastly does not log the destinations of proxied requests, and TLS still runs end to end between Firefox and the site. In June, Fastly said a move to MASQUE over HTTP/3 was planned for later this year.

On May 19, Firefox 151 added a location picker for users in the US, the UK, France, Germany and Canada, and on July 28 the VPN started rolling out on Android, in 29 countries. That list grew in September, and the release notes for Firefox 157 on Android, dated September 29, say the free VPN is "now available in more than 200 regions". The cap itself has now been lifted twice, first from June 9 to August 31 and again on November 10. The announcement does not say what happens on February 1.

On the device Path What the shop sees Firefox built-in VPN off direct connection Home ISP address the shopper's real city Firefox built-in VPN on CONNECT Fastly proxy AS54113 HTTPS sees the shopper's address and the destination host and port Mozilla exit in Paris 63.245.218.0/24, is_vpn Any other app on the same device direct connection, proxy not used Home ISP address the shopper's real city
The same shopper reaches the same shop from three addresses. Only page loads made by Firefox with the VPN switched on go through the proxy.

Thirty-eight /24s registered to Mozilla and announced by AS54113

We found no published list of exit addresses, but the registries do most of the work. On December 3, 2025, almost four months before launch, Mozilla carved 63.245.216.0/21 out of its own 63.245.208.0/20 at ARIN and named it MOZILLA-FIREFOX-VPN. The same name appeared the same day at the RIPE NCC, on 2a00:8c40:f000::/36. RIPEstat first saw Fastly announce routes from both on January 7, 2026.

That was not enough IPv4. On April 16 and 17, a month before the location picker, five more blocks were reallocated to Mozilla Corporation, and six more followed on June 5, four days before the summer promotion began. This is space taken from other holders, most of it cut from 45.58.192.0/18 and 149.143.128.0/18, which ARIN lists under WiredISP Inc. With the original /21 that makes 39 /24s, and on November 15 AS54113 originated 38 of them (63.245.223.0/24 was not in the routing table).

Product milestones Address registrations at ARIN and the RIPE NCC 2026 2027 no data cap no data cap Mar 24, 2026 Firefox 149 launch May 19 location picker Jul 28 Android rollout Nov 10 cap lifted again Nov 27 and 30 Black Friday, Cyber Monday Jan 31, 2027 offer ends Dec 3, 2025 MOZILLA-FIREFOX-VPN registered: a /21 and a /36 Apr 16 and 17 24 more IPv4 /24s Jun 5 7 more /24s
Each address registration came ahead of a product step. The two uncapped periods run from June 9 to August 31, 2026, and from November 10, 2026, to January 31, 2027. Registration dates from ARIN and the RIPE NCC, product dates from Mozilla.
BlockRegistered/24s announcedWhere our data places them
63.245.216.0/21Dec 3, 20257London, Los Angeles, Paris, Munich, Chicago, Toronto, Newark
45.58.232.0/21Apr 16, 20268Helsinki, Dublin, Milan, Amsterdam, Lisbon, Madrid, Kuala Lumpur, Auckland
45.58.212.0/22Apr 17, 20264Vienna, Brussels, Sofia, Copenhagen
45.58.240.0/22Apr 17, 20264Singapore, Sydney, Bangkok, Santiago
149.143.184.0/22Apr 17, 20264Bogotá, Querétaro, Vancouver, Johannesburg
198.145.136.0/22Apr 17, 20264Stockholm, Oslo, Tokyo, Accra
149.143.160.0/23Jun 5, 20262Hong Kong, Manila
45.56.195.0/24, 63.141.63.0/24, 104.238.251.0/24, 198.145.144.0/24, 198.145.237.0/24Jun 5, 20265Buenos Aires, Lima, San Francisco, Jakarta, São Paulo

On November 15 we looked up one address in each of the 38 /24s and in each of the 37 IPv6 /44s announced from the /36. All 75 came back with AS54113, connection type hosting, is_vpn true and every abuse flag false. The company is Mozilla Corporation on IPv4 and the registry name MOZILLA-FIREFOX-VPN on IPv6. This is the Paris range, trimmed to the fields that matter here:

{
  "company": { "domain": "mozilla.com", "name": "Mozilla Corporation", "type": "business" },
  "connection": {
    "asn": 54113,
    "organization": "Fastly, Inc.",
    "route": "63.245.218.0/24",
    "type": "hosting"
  },
  "ip": "63.245.218.10",
  "location": { "city": "Paris", "country": { "code": "FR" } },
  "security": {
    "is_abuser": false,
    "is_anonymous": true,
    "is_cloud_provider": true,
    "is_proxy": false,
    "is_relay": false,
    "is_residential_proxy": false,
    "is_threat": false,
    "is_tor": false,
    "is_vpn": true
  }
}

The address plan is one /24 per city. On IPv4, everyone who picks France leaves through 63.245.218.0/24, which is 256 addresses at most. The United States has four ranges and Canada two. Together the 38 ranges cover 34 countries and territories: 27 of the 29 countries on Mozilla's July list (Poland and Switzerland have no range of their own), plus Argentina, Brazil, Ghana, Hong Kong, Indonesia, Peru and the Philippines. The IPv6 /44s follow nearly the same order of cities. San Francisco and Jakarta are only on IPv4, and Seoul has a /44 but no /24 in Mozilla's name. Since July, AS54113 has also announced 149.143.171.0/24, which sits in WiredISP's 149.143.128.0/18. ARIN still lists it under WiredISP, and our data places it in Seoul with is_vpn true, so it is probably one more exit range.

We did not sit behind the proxy to count how often a session changes address, or how many addresses of a /24 carry traffic, so read 256 as a ceiling.

The country in the lookup is the one the user picked

Geolocation for these ranges can be accurate and still beside the point. Our data places 63.245.218.10 in Paris, and Mozilla says websites see the location of the proxy server. The person behind it may be in Lyon or in Montreal, and chose France from a menu.

iCloud Private Relay makes a useful comparison, because Fastly carries part of that as well, from the same AS. Fastly publishes a geofeed of 16,010 prefixes (8,005 IPv4 /31s and as many IPv6 prefixes) labeled with one of 234 country codes and, for 14,026 of them, a city. Every one of those entries appears in Apple's egress list. Relay hands the user an exit labeled with their approximate area, so the country in a lookup still describes the person. Firefox labels the exit with the place where the proxy runs and lets the user choose it. Our API returns is_relay for the first and is_vpn for the second.

Fastly's engineers had already described the problem in a position paper submitted in September 2025 to the IAB workshop on IP geolocation:

Presently there is no ontology which distinguishes between a geolocation claimed on behalf of a third party vs a claim made with respect to where the IP address, as a locator, is domiciled.

Six months later one AS was serving both kinds of claim, which is why a rule on the AS number cannot work. AS54113 originated 592 IPv4 prefixes on November 15. Among them are Fastly's CDN, the Private Relay exits, Mozilla's 38 ranges, and prefixes registered to PayPal, GitHub and New Relic.

The browser's time zone and Accept-Language, the billing and shipping countries and the account's history do not come from the address, so they still describe the shopper. And because the proxy covers only Firefox, the same customer's mobile app session and the click from a marketing email opened in another browser arrive from the real address.

A free browser VPN is not a rented residential proxy

Payment fraud wants an address that looks like the cardholder's neighbor. Residential proxies sell exactly that, and we have written about where the supply comes from, including backdoored TV boxes running up to three proxy SDKs each and at least one device inside the White House network. Firefox gives a fraudster a hosting range that is shared with other users who picked that country, registered to Mozilla in a public database and reachable only after signing in to an account, and none of that helps a stolen card pass as its owner.

To be fair, free and unlimited attracts its own abuse, and people already try to lift the proxy out of the browser. An October 27 feature request for a MASQUE client asks to chain through Firefox's exits because Fastly's addresses are "less likely to be flagged compared to Cloudflare WARP IPs". Mozilla says the product only covers browsing within Firefox, so a request from these ranges whose user agent or TLS fingerprint is not Firefox did not come from the product as shipped, which is a sharper test than the VPN flag.

The picker also makes another country's prices one click away. That is a pricing question, and the fix is to tie the price and the offer to the billing country.

Per-address velocity limits are where honest users will get hurt. A rule such as "five orders per IP per hour" was written with home connections in mind. On Black Friday, every Firefox VPN user who picked Germany shares 63.245.219.0/24 on IPv4.

Scoring the flag instead of denying it

Our recommendation is a small weight for is_vpn, no weight for the country mismatch that comes with it, and a step-up when the total gets high. The weights below are placeholders. Yours should come from your own chargeback data.

function networkScore(ip, order) {
  const s = ip.security;
  let score = 0;
  if (s.is_residential_proxy) score += 40;
  if (s.is_tor_exit) score += 40;
  if (s.is_proxy) score += 30;
  if (s.is_abuser || s.is_attacker) score += 25;
  if (s.is_vpn) score += 5;

  // A VPN's exit country is a user setting. Charging for the
  // mismatch too would count the same fact twice.
  const countryUsable = !(s.is_vpn || s.is_proxy || s.is_tor);
  if (countryUsable && ip.location.country.code !== order.billingCountry) {
    score += 15;
  }
  return score; // under 30 accept, 30 to 59 step up, 60 or more review
}

Step-up here means 3-D Secure or a one-time code sent to the account's email. It costs an honest shopper a few seconds, where a decline costs the order. Keep the velocity counters, but key them on the account, the card and the device, and drop the per-address limit for addresses flagged is_vpn.

The lookup says What that means At checkout iCloud Private Relay is_relay Exit assigned near the user, country still about right Accept use the country as usual Consumer VPN is_vpn, Firefox included Exit country picked by the user, range shared by many Accept, small score ignore the IP country Datacenter proxy is_proxy Traffic relayed by a server, often automated Step up 3-D Secure or email code Residential proxy is_residential_proxy A home address rented to pass as a local buyer Step up or review heaviest network weight Tor exit is_tor_exit Public exit shared by every Tor user Step up or decline set by policy, logged
One checkout rule per kind of anonymizer. Firefox's exits belong on the second row.

Log enough to check the decision in February: the address, connection.route, connection.asn, company.name, the security flags as they were at decision time, the score, the action and, later, whether the order was disputed. The chargeback rate of orders accepted from Mozilla's ranges, set against your baseline, is the number that should fix the weight next year.

Checklist for November 27 to January 31

  • Replace any hard decline on is_vpn at checkout with a score and a step-up.
  • Stop adding risk for an IP country mismatch when the address is a VPN, a proxy or a Tor exit.
  • Move order velocity limits from the address to the account, the card and the device.
  • Look twice at requests from Mozilla's ranges on AS54113 whose user agent is not Firefox.
  • Write no rule on AS54113 as a whole.
  • Set prices and regional restrictions from the billing or shipping country.
  • Store the flags and the outcome with every decision, and review the VPN segment after January 31.

Ipregistry returns the VPN, relay, proxy, residential proxy and Tor flags for each address, together with the announced prefix, the AS and the company that holds the block, which is what every rule above reads. We find VPN exits by using the services ourselves and by inference. You can see how your own checkout traffic splits with 20,000 free lookups to get started.

Engage customers with in-app updates using Noticeable Keep users in the loop Ship release notes that get read. Try Noticeable

Get started with 20,000 free lookups: sign up