MrSheepNET-DE
Cluster stats
| Netblocks | 3 |
| All fragments | 15 blocks across 10 clusters |
| Cluster ID | 194221263 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0c:e642:60::/44 | MrSheepNET-DE | RIPE | ASSIGNED | ● low |
| 2a0e:aa07:e008::/48 | MrSheepNET-DE | RIPE | ASSIGNED | ● low |
| 2a0e:aa07:f081::/48 | MrSheepNET-DE | RIPE | ASSIGNED | ● low |
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
0xDEADBEEF LTD
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
DEADBEEF-MNT
DUMY-RIPE
DUMY-RIPE