STANLEY-SECURITY-NET

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks8
IPv6 3 prefixes (largest 2a00:2381:c1d5::/48)
Also registered under this name 13 netblocks across 5 separate records
Record ID236535804
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
194.251.129.152/29 STANLEY-SECURITY-NET RIPE ASSIGNED PA ● low
194.251.129.160/29 STANLEY-SECURITY-NET RIPE ASSIGNED PA ● low
194.251.129.168/29 STANLEY-SECURITY-NET RIPE ASSIGNED PA ● low
194.251.129.192/29 STANLEY-SECURITY-NET RIPE ASSIGNED PA ● low
194.251.129.216/29 STANLEY-SECURITY-NET RIPE ASSIGNED PA ● low
2a00:2381:c1d5::/48 STANLEY-SECURITY RIPE AGGREGATED-BY-LIR ● low
2a00:2381:c1d5::/56 STANLEY-SECURITY RIPE ASSIGNED ● low
2a00:2381:c1d5:100::/56 STANLEY-SECURITY RIPE ASSIGNED ● low

IPv6 ranges (3)

Footprint over time

11 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-09-06

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 (3)

These blocks are registered to STANLEY-SECURITY-NET 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:c1d5::/48 /48 authorized for AS2856 — British Telecommunications Limited
2a00:2381:c1d5::/56 /56 authorized for AS2856 — British Telecommunications Limited
2a00:2381:c1d5:100::/56 /56 authorized for AS2856 — British Telecommunications Limited

NIC Handles

BTNET-MNT DATANET-NOC DUMY-RIPE DUMY-RIPE