IDNIC-UNIMED-ID
Data as of 2026-08-09
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 512 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:df4:5000::/48) |
| Cluster ID | 218103306 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.54.172.0/24 | IDNIC-UNIMED-ID | APNIC | ASSIGNED PORTABLE | ● medium |
| 103.242.233.0/24 | IDNIC-UNIMED-ID | APNIC | ASSIGNED PORTABLE | ● medium |
| 2001:df4:5000::/48 | IPv6-IDNIC-UNIMED-ID | APNIC | ASSIGNED PORTABLE | ● medium |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:df4:5000::/48 |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
RPKI-inferred operator
Universitas Negeri Medan
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
MNT-APJII-ID
MWD3-AP
MWD3-AP