87.121.125.0/24
AS200590 · NLS Kazakhstan LLC
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›Summary
Country |
Kazakhstan
|
Domain | nls.kz |
ASN | AS200590 |
Registry | RIPE |
ID | KZ-NLS |
WHOIS Details
inetnum: 87.121.125.0 - 87.121.125.255 netname: KZ-NLS descr: NLS Networks for Clients org: ORG-NKL4-RIPE country: KZ admin-c: NND10-RIPE tech-c: NND10-RIPE mnt-routes: MNT-SEABAK mnt-domains: MNT-SEABAK status: ASSIGNED PA mnt-by: MNT-NETERRA created: 2025-06-05T09:30:22Z last-modified: 2025-06-05T10:21:06Z source: RIPE abuse-email: ncc@nls.kz abuse-c: NND10-RIPE abuse-org: ORG-NKL4-RIPE organisation: ORG-NKL4-RIPE org-name: NLS Kazakhstan LLC country: KZ org-type: LIR address: AL-FARABI AVENUE, 95 KV 115 address: A15E3X9 address: Almaty address: KAZAKHSTAN phone: +77273572121 e-mail: ncc@nls.kz admin-c: DR11653-RIPE tech-c: DR11653-RIPE abuse-c: NND10-RIPE mnt-ref: RIPE-NCC-HM-MNT mnt-ref: AP99722-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: AP99722-MNT created: 2015-04-16T07:44:30Z last-modified: 2025-06-11T09:40:02Z source: RIPE mnt-ref: MNT-NETERRA abuse-email: ncc@nls.kz abuse-c: NND10-RIPE abuse-org: undefined role: NLSKZ NCC Department address: AL-FARABI AVENUE, 95 KV 115, ALMATY, KAZAKHSTAN e-mail: ncc@nls.kz abuse-mailbox: ncc@nls.kz admin-c: DR11653-RIPE nic-hdl: NND10-RIPE mnt-by: AP99722-MNT created: 2015-04-22T04:53:59Z last-modified: 2025-06-11T09:39:17Z source: RIPE route: 87.121.125.0/24 origin: AS200590 descr: KZ-NLS created: 2025-06-05T11:10:03Z last-modified: 2025-06-05T11:10:03Z source: RIPE mnt-by: MNT-SEABAK
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
No IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
IP Address | ASN | Details |
---|---|---|
186.30.5.136 |
0.97ms from Bogota,
CO
|
|
91.82.35.104 |
5.11ms from Budapest,
HU
|
|
200.129.48.40 |
1.11ms from Fortaleza,
BR
|
|
125.163.20.184 |
3.95ms from Jakarta,
ID
|
|
45.145.86.216 |
0.28ms from London,
GB
|
|
13.233.23.88 |
0.18ms from Mumbai,
IN
|
|
66.153.25.8 |
9.87ms from New York City,
US
|
|
191.235.40.216 |
0.18ms from Sao Paulo,
BR
|
|
83.182.51.136 |
4.19ms from Stockholm,
SE
|
|
84.218.26.24 |
0.81ms from Stockholm,
SE
|
|
54.79.10.104 |
0.45ms from Sydney,
AU
|
|
42.148.106.136 |
13.48ms from Tokyo,
JP
|
|
77.234.228.248 |
6.43ms from Bratislava,
SK
|
|
5.13.123.136 |
7.41ms from Bucharest,
RO
|
|
191.85.81.120 |
1.47ms from Buenos Aires,
AR
|
|
94.220.169.184 |
8.58ms from Frankfurt am Main,
DE
|
|
82.35.133.152 |
7.44ms from London,
GB
|
|
76.170.234.232 |
4.01ms from Los Angeles,
US
|
|
151.48.95.8 |
8.88ms from Milan,
IT
|
|
67.253.217.40 |
19.62ms from Secaucus,
US
|
|
36.239.143.184 |
5.27ms from Taichung,
TW
|
|
119.241.143.184 |
14.88ms from Tokyo,
JP
|
|
20.210.49.248 |
0.13ms from Tokyo,
JP
|
|
20.78.248.56 |
0.18ms from Tokyo,
JP
|
|
102.158.152.40 |
2.20ms from Tunis,
TN
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
What are IP address ranges?
IP address ranges, or netblocks, are groups of related IP addresses. They are usually represented as a base IP address, followed by a slash, and then a netmask which represents how many IP addresses are contained within the netblock. This format is known as CIDR. You'll also sometimes see netblocks given as a start ip address, and an end ip address, or an ip address range.
Traffic works its way around the internet based on the routing table, which contains a list of networks and their associated netblocks.
An API built with users in mind: reliable, accurate, and easy-to-use
Discover why industry-leading companies around the globe love our data. IPinfo's accurate insights fuel use cases from cybersecurity, data enrichment, web personalization, and much more.
Our IP tools
Explore all toolsSummarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs