FUTURE DOT NET
BGP inherited
Limited data: only 2 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
| Netblocks | 2 · 766 IPv4 addresses |
| Cluster ID | 210211435 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 36.50.116.0/24 | FUTURE DOT NET | BGP | ANNOUNCED | ● high |
| 36.50.116.0/23 | FUTURE DOT NET | APNIC | ALLOCATED PORTABLE | ● low |
Possibly related to this organisation
what's this?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.
- MAX-N-FUTURE via Invitech ICT Services Kft. sub-allocation
- FUTURE-ITALIA sub-allocation
- NETDIRECT-CUST-FUTUREELECTRONICS sub-allocation
- FUTUREMARK-FI via DNA Oyj sub-allocation
- Future Mort via Vodafone Group PLC sub-allocation
- Carr Future B sub-allocation
- Pipex Futuresinternational via Wavenet Limited sub-allocation
- FUTURE-LINE via KPN B.V. sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
No discrepancies found among checked blocks.
NIC Handles
AF848-AP
APNIC-HM
AS152163
ORG-FN23-AP
SSA46-AP
SSA46-AP