Mr Sheep NET
MrSheepNET
Registry
Cluster stats
| Netblocks | 3 |
| All fragments | 15 blocks across 10 clusters |
| Cluster ID | 195490705 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| 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::/44 | MrSheepNET | RIPE | ASSIGNED | ● low |
| 2a0c:e642:40::/44 | MrSheepNET | RIPE | ASSIGNED | ● low |
| 2a0e:aa07:f080::/48 | MrSheepNET | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (3)
These blocks are registered to MrSheepNET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a0c:e642::/44 /44 | authorized for AS60326 — 0xDEADBEEF LTD |
| 2a0c:e642:40::/44 /44 | authorized for AS60326 — 0xDEADBEEF LTD |
| 2a0e:aa07:f080::/48 /48 | authorized for AS60326 — 0xDEADBEEF LTD |
NIC Handles
DEADBEEF-MNT
DUMY-RIPE
DUMY-RIPE