JSC InterDnestrCom
JSC InterDnestrCom (IDC)
Cluster stats
| Netblocks | 28 |
| All fragments | 26,741 blocks across 11,731 clusters |
| Cluster ID | 191871679 |
| Registry | PEERINGDB |
| Customers | find 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 (28)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.81.194.70/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 80.81.195.70/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 80.249.208.97/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.72/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 185.1.192.174/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 193.178.185.62/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 193.239.117.123/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 195.66.224.200/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 195.208.208.89/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 198.32.160.123/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 206.71.141.44/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 206.72.211.27/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 206.108.35.141/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 208.115.136.192/32 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:4::1547:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1::a500:1547:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:504:13::211:27/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1a::35:141/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:504:77::44/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::60b:0:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::60b:0:2/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a500:1547:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::60b:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a500:1547:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:19:1::60b:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::208:89/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:a0::60b:0:1/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:72/128 | JSC InterDnestrCom (IDC) | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
82.1%
of checked blocks have valid RPKI ROA coverage
(23 of 28)
No discrepancies found among checked blocks.
NIC Handles
AS1547