MORGAN-SINDALL

Data as of 2026-11-01
Unresolved
This organisation
Netblocks8
IPv6 6 prefixes (largest 2a00:2381:fcd1::/48)
Record ID266020016
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution unresolved
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 (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.128.170.64/28 MORGAN-SINDALL-PLC RIPE ASSIGNED PA ● low
217.33.168.16/28 MORGAN-SINDALL RIPE ASSIGNED PA ● low
2a00:2381:fcd1::/48 MORGAN-SINDALL-PLC RIPE AGGREGATED-BY-LIR ● low
2a00:2381:fcd1::/56 MORGAN-SINDALL RIPE ASSIGNED ● low
2a00:2381:fcd1:100::/56 MORGAN-SINDALL RIPE ASSIGNED ● low
2a00:2381:fcd1:200::/56 MORGAN-SINDALL-PLC RIPE ASSIGNED ● low
2a00:2381:ffff:c4::/64 MORGAN-SINDALL RIPE ASSIGNED ● low
2a00:2381:ffff:c5::/64 MORGAN-SINDALL RIPE ASSIGNED ● low

IPv6 ranges (6)

CIDR
2a00:2381:fcd1::/48
2a00:2381:fcd1:100::/56
2a00:2381:fcd1:200::/56
2a00:2381:fcd1::/56
2a00:2381:ffff:c4::/64
2a00:2381:ffff:c5::/64

Footprint over time

19 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-11-01

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
Possible discrepancies (4)

These blocks are registered to MORGAN-SINDALL 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.

2a00:2381:fcd1::/48 /48 authorized for AS2856 — British Telecommunications Limited
2a00:2381:fcd1:100::/56 /56 authorized for AS2856 — British Telecommunications Limited
2a00:2381:fcd1:200::/56 /56 authorized for AS2856 — British Telecommunications Limited
2a00:2381:fcd1::/56 /56 authorized for AS2856 — British Telecommunications Limited

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE