Data as of Nov 11, 2026
95.182.0.0/21
730 residential-proxy exits · 30 daysBaynur and P Ltd.
Residential-proxy exits
Proxy exits
730
36% of its addresses · 30 days
Spread
8 of 8
/24s with at least one exit
Providers
109
selling exits here
Oct 12, 2026 – Nov 10, 2026
Exits seen per day
54K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 95.182.3.0/24 | 0 | 104 | |
| 95.182.5.0/24 | 0 | 97 | |
| 95.182.1.0/24 | 0 | 95 | |
| 95.182.4.0/24 | 0 | 93 | |
| 95.182.0.0/24 | 0 | 89 | |
| 95.182.7.0/24 | 0 | 89 | |
| 95.182.6.0/24 | 0 | 82 | |
| 95.182.2.0/24 | 0 | 81 |
Proxy providers listing exits
- 711Proxy
- 911Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PrivateByte
- PrivateProxy
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxyma
- PuraRoute
- Q2IP
- QUANTICDATA
- RH7Proxy
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TORCHPROXIES_BASIC
- TORCHPROXIES_PREMIUM
- TORCHPROXIES_X
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
- VitalData
- VitalExclusive
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 95. | 6,144 | KZ-BAINUR-20090205 | Baynur and P Ltd. (ORG-BAPL2-RIPE) · KZ | ALLOCATED PA | Oct 24, 2014 | abuse@ |
| └ 95.182.0.0/20 | 4,096 | BAYNUR-NET | unknown | ASSIGNED PA | Aug 4, 2016 | abuse@ via KZ-BAINUR-20090205 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Registry
Holder
- Organization
- Baynur and P Ltd.
- Handle
- ORG-BAPL2-RIPE
- Range
- 95.
182. 0. 0 - 95. 182. 23. 255 - Registration type
- ALLOCATED PA
- Record created
- Oct 24, 2014
Origin network
AS59443
KZ
- Name
- Baynur and P Ltd.
- Type
- Internet provider
- Registered
- Jul 12, 2012
- Domain
- bainur.kz
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2014
- Current origin since
- May 2014 · 13 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS59443 | RIPE | route object | BAINUR-MNT | Apr 29, 2014 |
Whois
Registration for this announcement
- Range
- 95.
182. 0. 0/ 20 - Netname
- BAYNUR-NET
- Registrant country
- KZ
- Organization
- Not stated by the registry
- Type
- ASSIGNED PA
- Created
- Aug 4, 2016
- Updated
- Aug 4, 2016
- Maintainer
- BAINUR-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Feb 5, 2009
- Status
- assigned
Report abuse
Abuse contact
- abuse@
bainur. kz - Name
- Baynur Network Administrator
- Handle
- BNA26-RIPE