Durham County Council

Data as of 2026-08-09
BGP inherited
Limited data: only 3 ranges found registered under this exact name. This may not reflect the organisation's full internet footprint — many companies' web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
Netblocks3 · 4,104 IPv4 addresses
IPv6 1 prefix (largest 2a00:2381:f058::/48)
Cluster ID218171677
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
217.23.224.0/20 Durham County Council BGP ANNOUNCED ● high
62.252.145.208/29 DURHAM-COUNTY-COUNCIL RIPE ASSIGNED PA ● low
2a00:2381:f058::/48 DURHAM-COUNTY-COUNCIL RIPE AGGREGATED-BY-LIR ● low

IPv6 ranges (1)

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (2 of 4)
Possible discrepancies (1)

These blocks are registered to Durham County Council 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:f058::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AS15770 AS5089-MNT BTNET-MNT DERWENTSIDE-MNT DERWENTSIDE-MNT DUMY-RIPE DUMY-RIPE ORG-DDC1-RIPE RIPE-NCC-HM-MNT