Data as of Nov 8, 2026
95.57.120.0/24
1 residential-proxy exit · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
307 observations
Proxy providers listing exits
- 2Captcha
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- FlashProxy
- GonzoProxy
- Infatica
- LemonBright
- Novada
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyWing
- Proxyma
- Shifter
- Thordata
- ThunderProxy
- VibeProxies
- VitalExclusive
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 95.57.0.0/17 since Aug 2016 | AS9198 | Residential | 7,643 147 always on | JSC Kazakhtelecom | |
| 95.56.0.0/14 since Oct 2008 | AS9198 | Residential | 56,993 922 always on | JSC Kazakhtelecom |
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.56.0.0/14 | 262,144 | KZ-KAZAKTELECOM-20080923 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Sep 23, 2008 | abuse@ |
| └ 95.57.120.0/30 | 4 | CHING_ | ZKO | ASSIGNED PA | Jan 24, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.8/30 | 4 | GU_ | ZKO | ASSIGNED PA | Feb 21, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.12/30 | 4 | PRAVITELSTVO_ | URALSK | ASSIGNED PA | Feb 27, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.16/30 | 4 | BKOSOCIO | unknown | ASSIGNED PA | May 19, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.20/30 | 4 | KHALISAGINOV | URALSK | ASSIGNED PA | Jan 6, 2021 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.24/30 | 4 | LIFTMONTAZH | URALSK | ASSIGNED PA | Nov 17, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.28/30 | 4 | LIFTMONTAZH | URALSK | ASSIGNED PA | Nov 17, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.32/30 | 4 | CHAPAI_ | unknown | ASSIGNED PA | Nov 12, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.36/30 | 4 | TOOPACKAGINGSYSTEMS | unknown | ASSIGNED PA | Sep 24, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.44/30 | 4 | UPRZDRAV | GU Upravlenie zdravoohraneniya ZKO | ASSIGNED PA | Nov 3, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.48/30 | 4 | UPRZDRAV | GU Upravlenie zdravoohraneniya ZKO | ASSIGNED PA | Nov 3, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.52/30 | 4 | UPRZDRAV | GU Upravlenie zdravoohraneniya ZKO | ASSIGNED PA | Nov 3, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.56/30 | 4 | ZHANGALA_ | ZKO | ASSIGNED PA | May 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.60/30 | 4 | Syrym_ | Syrym obrazavaniya | ASSIGNED PA | Oct 23, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.64/30 | 4 | Syrym_ | Syrym obrazavaniya | ASSIGNED PA | Oct 23, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.72/30 | 4 | GKPNAPHVUPRAVZDRAV | unknown | ASSIGNED PA | Jun 26, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.76/30 | 4 | IP_ | URALSK | ASSIGNED PA | Jun 5, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.80/30 | 4 | JAYIQPRESS | URALSK | ASSIGNED PA | Jul 19, 2023 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.84/30 | 4 | KGU_ | unknown | ASSIGNED PA | Oct 19, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.92/30 | 4 | IPKANDI | URALSK | ASSIGNED PA | Oct 19, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.96/30 | 4 | ZHAYKKALASHAGY | URALSK | ASSIGNED PA | Aug 13, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.100/30 | 4 | FORESTCONSERVATIONORDA | unknown | ASSIGNED PA | Oct 15, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.108/30 | 4 | ARKHIVE | ARKHIVE | ASSIGNED PA | Oct 12, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.112/30 | 4 | AKIMAT_ | Myhambetova d 50. pos Aktan in Chingrlay rn ZKO | ASSIGNED PA | Dec 6, 2021 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.116/30 | 4 | IPCLOUDATLAS | unknown | ASSIGNED PA | Sep 29, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.120/30 | 4 | OTD_ | URALSK | ASSIGNED PA | Feb 13, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.124/30 | 4 | TOODOKTORSAMAT | URALSK | ASSIGNED PA | Oct 7, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.128/30 | 4 | IP_ | URALSK | ASSIGNED PA | Oct 2, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.132/30 | 4 | IPTKV | unknown | ASSIGNED PA | Oct 23, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.136/30 | 4 | SOSH51 | URALSK | ASSIGNED PA | Feb 13, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.140/30 | 4 | ARKHIVE | ARKHIVE | ASSIGNED PA | Oct 1, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.144/30 | 4 | ARKHIVE | ARKHIVE | ASSIGNED PA | Oct 1, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.148/30 | 4 | GU_ | unknown | ASSIGNED PA | Oct 1, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.152/30 | 4 | GU_ | in Zhimpiti | ASSIGNED PA | May 29, 2023 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.156/30 | 4 | GU_ | unknown | ASSIGNED PA | Oct 1, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.160/30 | 4 | GU_ | unknown | ASSIGNED PA | Oct 1, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.164/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.168/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.172/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.176/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.180/30 | 4 | KGU_ | unknown | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.184/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.188/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.192/30 | 4 | WKETU | URALSK | ASSIGNED PA | Sep 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.196/30 | 4 | OTDEL_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.200/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.204/30 | 4 | KGU_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.208/30 | 4 | GLOBALINFOSYSTEM | URALSK | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.212/30 | 4 | GY_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.216/30 | 4 | GUMKOLLEJ | URALSK | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.220/30 | 4 | GUMKOLLEJ | URALSK | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.224/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.228/30 | 4 | GU_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.232/30 | 4 | SYRYM_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.236/30 | 4 | SYRYM_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.240/30 | 4 | GKP_ | unknown | ASSIGNED PA | Sep 29, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.244/30 | 4 | GKP_ | unknown | ASSIGNED PA | Dec 2, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.248/30 | 4 | GKP_ | unknown | ASSIGNED PA | Dec 2, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.120.252/30 | 4 | AKZHROO | unknown | ASSIGNED PA | May 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
256 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 236 | 92% | 59 | |
| Residential | 20 | 7.8% | 5 |
Network & registry
Origin network
AS9198
KZ
- Name
- JSC Kazakhtelecom
- Type
- Internet provider
- Registered
- Feb 23, 1999
- Domain
- telecom.kz
- Website
- www.telecom.kz
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Apr 2013
- Current origin since
- Aug 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 95.57.120.0/24 | AS9198 | /24 | RIPE | RPKI valid |
| 95.57.0.0/17 | AS9198 | /17 | RIPE | Too specific |
| 95.56.0.0/14 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Apr 26, 2010 |
Whois
Registration for this announcement
- Range
- 95.
56. 0. 0/ 14 - Netname
- KZ-KAZAKTELECOM-20080923
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Sep 23, 2008
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Sep 23, 2008
- Status
- assigned
Report abuse
Abuse contact
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE