Afranet
fan-avaze
Registry
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 |
| Cluster ID | 205440766 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 3 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 |
|---|---|---|---|---|
| 31.47.32.44/30 | fan-avaze | RIPE | ASSIGNED PA | ● low |
| 46.102.132.0/25 | fan-Avaze | RIPE | ASSIGNED PA | ● 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.
- Noavarn-Fan-Avazeh via Afranet sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
No discrepancies found among checked blocks.
NIC Handles
AFRA-MNT-NESH-1
DUMY-RIPE
DUMY-RIPE