DINETKAN
Cluster stats
Netblocks17
Cluster ID193390004
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (17)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.252.147.71/32 DINETKAN PEERINGDB ASSIGNED ● high
43.254.82.104/32 DINETKAN PEERINGDB ASSIGNED ● high
49.213.56.45/32 DINETKAN PEERINGDB ASSIGNED ● high
103.19.77.85/32 DINETKAN PEERINGDB ASSIGNED ● high
103.61.232.177/32 DINETKAN PEERINGDB ASSIGNED ● high
103.162.254.142/32 DINETKAN PEERINGDB ASSIGNED ● high
119.11.185.187/32 DINETKAN PEERINGDB ASSIGNED ● high
123.108.11.31/32 DINETKAN PEERINGDB ASSIGNED ● high
123.108.12.32/32 DINETKAN PEERINGDB ASSIGNED ● high
2001:7fa:2:5::32f/128 DINETKAN PEERINGDB ASSIGNED ● high
2001:7fa:2:5::42e/128 DINETKAN PEERINGDB ASSIGNED ● high
2001:7fa:f::575/128 DINETKAN PEERINGDB ASSIGNED ● high
2001:df1:d440:1::b1/128 DINETKAN PEERINGDB ASSIGNED ● high
2001:df5:7880:0:2:51e0:0:1/128 DINETKAN PEERINGDB ASSIGNED ● high
2001:df6:480:0:2:51e0:0:1/128 DINETKAN PEERINGDB ASSIGNED ● high
2401:91e0:31::1520:32:1/128 DINETKAN PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:15:2032:1/128 DINETKAN PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: D how networks compare →
41.2% of checked blocks have valid RPKI ROA coverage (7 of 17)
No discrepancies found among checked blocks.

NIC Handles

AS152032