BINBOX-Toronto
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 4 · 1,024 IPv4 addresses |
| Cluster ID | 216764700 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 84.247.66.0/24 | BINBOX-Toronto | RIPE | SUB-ALLOCATED PA | ● low |
| 84.247.73.0/24 | BINBOX-Toronto | RIPE | SUB-ALLOCATED PA | ● low |
| 84.247.74.0/24 | BINBOX-Toronto | RIPE | SUB-ALLOCATED PA | ● low |
| 84.247.78.0/24 | BINBOX-Toronto | RIPE | SUB-ALLOCATED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
RPKI-inferred operator
TNGNET B.V.
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
ORG-PC843-RIPE
PC20160-RIPE
netutils-mnt