87.121.124.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.124.0 - 87.121.124.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:28:53Z last-modified: 2025-06-05T10:20:45Z 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.124.0/24 origin: AS200590 descr: KZ-NLS created: 2025-06-05T11:08:37Z last-modified: 2025-06-05T11:08:37Z 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 |
---|---|---|
178.227.32.104 |
17.27ms from Amsterdam,
NL
|
|
84.46.228.248 |
0.46ms from Atlanta,
US
|
|
178.222.218.168 |
2.16ms from Belgrade,
RS
|
|
15.181.113.232 |
0.63ms from Boston,
US
|
|
23.54.95.184 |
0.31ms from Chennai,
IN
|
|
79.196.173.8 |
7.61ms from Frankfurt am Main,
DE
|
|
117.6.85.168 |
1.29ms from Hanoi,
VN
|
|
109.251.52.24 |
0.89ms from Kyiv,
UA
|
|
64.175.73.104 |
6.47ms from Miami,
US
|
|
45.223.235.8 |
0.12ms from Milan,
IT
|
|
182.108.227.104 |
4.11ms from Nanchang,
CN
|
|
38.96.131.216 |
0.72ms from New York City,
US
|
|
74.88.110.104 |
10.36ms from New York City,
US
|
|
123.221.32.200 |
5.32ms from Osaka,
JP
|
|
166.49.235.136 |
2.97ms from Oslo,
NO
|
|
131.100.80.40 |
8.95ms from Porto Alegre,
BR
|
|
34.194.156.152 |
0.17ms from Reston,
US
|
|
221.153.29.248 |
1.51ms from Seoul,
KR
|
|
61.227.244.104 |
4.31ms from Taichung,
TW
|
|
45.37.38.136 |
10.41ms from Ashburn,
US
|
|
40.27.200.104 |
0.20ms from Ashburn,
US
|
|
103.246.16.216 |
0.86ms from Bangkok,
TH
|
|
67.167.44.168 |
4.83ms from Chicago,
US
|
|
120.26.37.88 |
2.18ms from Hangzhou,
CN
|
|
14.171.45.216 |
2.73ms from Hanoi,
VN
|
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