ccTLD-KazNIC-NET
Data as of 2026-10-18
BGP inherited
This organisation
| Netblocks | 3 · 256 IPv4 addresses |
| IPv6 | 2 prefixes (largest 2001:678:98::/48) |
| Also registered under this name | 4 netblocks across 2 separate records |
| Record ID | 250828565 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 194.0.21.0/24 | ccTLD-KazNIC-NET | RIPE | ASSIGNED ANYCAST | ● high |
| 2001:678:98::/48 | ccTLD-KazNIC-NET | RIPE | ASSIGNED ANYCAST | ● high |
| 2a01:7640:9000::/48 | ccTLD-KazNIC-NET | RIPE | ASSIGNED | ● high |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
RPKI-inferred operator
Association of IT Companies of Kazakhstan
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-ITK
ORG-AoIC1-RIPE
RIPE-NCC-END-MNT