Browsec VPN
Browsec provides VPN browser extensions and applications for desktop and mobile devices.
- IPv4 prefixes
- 43
- IPv6 prefixes
- 0
- Public IP examples
- 12
Coverage: Browser proxy endpoints from Browsec's public server list, including its returned free and paid groups. Country tags are service selections, not verified physical locations.Resolved 43 of 43 published hostnames
- Last successful capture
- 2026-11-22 02:20 UTC
- Last source check
- 2026-11-22 02:20 UTC
- Product category
- consumer vpn
- Catalog status
- active
This capture contains 43 IP prefixes. Single-address observations use /32 for IPv4 and /128 for IPv6. Counts describe listed network records, not active servers or users.
Published service locations
Country tags attached to the captured connection addresses by their source. These are service locations, not measured IP geography or the provider’s complete country list. An address may appear under more than one location.
15 of 15 service locations
| AustriaAT | 2 |
| BelgiumBE | 1 |
| BulgariaBG | 3 |
| CroatiaHR | 3 |
| CyprusCY | 2 |
| FinlandFI | 3 |
| FranceFR | 1 |
| GermanyDE | 4 |
| GreeceGR | 3 |
| LatviaLV | 6 |
| LithuaniaLT | 4 |
| NetherlandsNL | 6 |
| PolandPL | 1 |
| TürkiyeTR | 1 |
| United StatesUS | 3 |
Approximate sample locations
Basis: sampled IP geolocation. This is not a measure of Browsec VPN’s complete coverage or its users’ locations. Records without a country are omitted, so published locations may cover only part of the inventory.
12 country-tagged records
| Country | Sampled IPs | Relative record count |
|---|---|---|
| 2 | ||
| 2 | ||
| 2 | ||
| 2 | ||
| 1 | ||
| 1 | ||
| 1 | ||
| 1 |
Published prefix counts over time
Daily retained source observations. Counts describe network inventory, not connections, traffic or active servers.
View exact daily prefix counts
| UTC date | IPv4 prefixes | IPv6 prefixes |
|---|---|---|
| 2026-11-22 | 43 | 0 |
| 2026-11-21 | 43 | 0 |
| 2026-11-20 | 43 | 0 |
| 2026-11-19 | 43 | 0 |
| 2026-11-18 | 43 | 0 |
| 2026-11-17 | 69 | 1 |
| 2026-11-16 | 69 | 1 |
| 2026-11-15 | 69 | 1 |
| 2026-11-14 | 69 | 1 |
| 2026-11-13 | 69 | 1 |
| 2026-11-12 | 69 | 1 |
| 2026-11-11 | 69 | 1 |
| 2026-11-10 | 69 | 1 |
| 2026-11-09 | 69 | 1 |
| 2026-11-08 | 69 | 1 |
ASNs represented in the public sample
Network ownership can differ from the service brand. Counts are sampled addresses, not a provider’s complete ASN footprint.
IP address examples
Each address keeps its source role and its own location basis. Connection infrastructure and published range examples are not confirmed exits unless the source explicitly identifies them as exits. For prefix-list sources, an IP example is the first address in its range, not a measured reachable exit.
The example filter searches only the addresses shown here. Look up another IP · Check my public IP
12 of 12 public examples
The cited source reports these settings for individual examples, not every provider feature. Protocol and port lists are independent; their combinations and reachability were not tested.
| IP address and source role | Location evidence | ASN and network | Evidence |
|---|---|---|---|
| 5.22.210.149connectionPublished protocol: HTTPS proxyPublished port: 22816 | The NetherlandsApproximate IPQuery geolocationAmsterdam · Geo checked 2026-11-22 | AS202053UpCloud Ltd | provider-browsec |
| 46.183.184.74connectionPublished protocol: HTTPS proxyPublished port: 18436 | CroatiaApproximate IPQuery geolocationZagreb · Geo checked 2026-11-22 | AS25467Akton d.o.o. | provider-browsec |
| 80.69.175.18connectionPublished protocol: HTTPS proxyPublished port: 21185 | FinlandApproximate IPQuery geolocationEspoo · Geo checked 2026-11-22 | AS202053UpCloud Ltd | provider-browsec |
| 89.124.11.9connectionPublished protocol: HTTPS proxyPublished port: 443 | LithuaniaApproximate IPQuery geolocationVilnius · Geo checked 2026-11-22 | AS215373Sabiedriba ar ierobezotu atbildibu DELSKA Latvia | provider-browsec |
| 94.237.109.208connectionPublished protocol: HTTPS proxyPublished port: 11096 | The NetherlandsApproximate IPQuery geolocationAmsterdam · Geo checked 2026-11-22 | AS202053UpCloud Ltd | provider-browsec |
| 151.236.5.96connectionPublished protocol: HTTPS proxyPublished port: 14514 | AustriaApproximate IPQuery geolocationVienna · Geo checked 2026-11-22 | AS57169EDIS GmbH | provider-browsec |
| 185.26.50.216connectionPublished protocol: HTTPS proxyPublished port: 9082 | FinlandApproximate IPQuery geolocationEspoo · Geo checked 2026-11-22 | AS202053UpCloud Ltd | provider-browsec |
| 185.193.50.120connectionPublished protocol: HTTPS proxyPublished port: 1961 | CroatiaApproximate IPQuery geolocationZagreb · Geo checked 2026-11-22 | AS25467Akton d.o.o. | provider-browsec |
| 185.219.159.93connectionPublished protocol: HTTPS proxyPublished port: 9164 | LatviaApproximate IPQuery geolocationRiga · Geo checked 2026-11-22 | AS215373Sabiedriba ar ierobezotu atbildibu DELSKA Latvia | provider-browsec |
| 192.71.166.60connectionPublished protocol: HTTPS proxyPublished port: 20879 | GreeceApproximate IPQuery geolocationThessaloníki · Geo checked 2026-11-22 | AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | provider-browsec |
| 195.123.225.193connectionPublished protocol: HTTPS proxyPublished port: 3213 | BulgariaApproximate IPQuery geolocationSofia · Geo checked 2026-11-22 | AS59729ROUTE 95 LLC | provider-browsec |
| 212.52.16.87connectionPublished protocol: HTTPS proxyPublished port: 24047 | GreeceApproximate IPQuery geolocationThessaloníki · Geo checked 2026-11-22 | AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | provider-browsec |
IP range examples
Single-address observations appear as /32 or /128 prefixes. A larger prefix is shown only when supported by the source. Listed addresses are not necessarily reachable, and source attribution alone is not a reason to block them.
| Network prefix | Source role | Evidence |
|---|---|---|
| 5.22.210.149/32 | connection | provider-browsec |
| 5.187.33.144/32 | connection | provider-browsec |
| 37.203.37.6/32 | connection | provider-browsec |
| 46.183.184.74/32 | connection | provider-browsec |
| 51.158.202.56/32 | connection | provider-browsec |
| 51.158.204.46/32 | connection | provider-browsec |
| 51.158.204.180/32 | connection | provider-browsec |
| 80.69.175.18/32 | connection | provider-browsec |
| 85.9.201.68/32 | connection | provider-browsec |
| 89.111.26.163/32 | connection | provider-browsec |
Sources and limits
Checked is the latest collection attempt. Captured is the last successful collection. Published is the publisher's date, when supplied. Inventory changed is when different source data was last observed. None of these dates confirms that an address is reachable. An unspecified license does not grant permission to redistribute a full dataset.
| Source and role | Checks and capture dates | Status and license |
|---|---|---|
| Browsec VPN official connection inventory ↗connectionResolved 43 of 43 published hostnames | Checked 2026-11-22 02:20 UTCCaptured 2026-11-22 02:20 UTCPublished 2026-11-21 08:10 UTCInventory changed 2026-11-18 02:22 UTC | currentPublic provider metadata; no dataset redistribution license asserted |
Official service references
Public previews contain up to 10 ranges, 12 IP examples and 10 ASN rows. Sample geolocation is approximate and does not describe the provider's entire network. Use the VPN checker to see the API's current classification for an address.
All VPN providers · Official crawler networks · IPQuery sources and methods