TAYLOR_COCKS_VFW
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 5 blocks across 4 clusters |
| Cluster ID | 204898594 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 212.87.72.32/30 | TAYLOR_COCKS_VFW | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TAYLOR COCKS” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- TAYLOR_COCKS 2 blocks
- TAYLOR-COCKS-NORAD 1 blocks
- TAYLOR_COCKS_INET3 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- TAYLORCOCKS_NORAD sub-allocation
- TAYLOR-COCKS-NORAD sub-allocation
- TAYLOR_COCKS_INET3 sub-allocation
- Taylorcocks sub-allocation
- TCIT-TAYLORCOCKS-WIFI sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
NEWNET-MNT