MOZES
BGP inherited
Cluster stats
| Netblocks | 10 |
| Registered in | Israel (8) · Netherlands (1) |
| All fragments | 30 blocks across 8 clusters |
| Cluster ID | 209275125 |
| 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 | 5 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
10
0 netblocks since 2026-07-05
2026-07-05
peak 10
2026-07-19
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.178.251.112/28 | MOZES-LTD | RIPE | ASSIGNED PA | ● low |
| 192.117.141.144/28 | Mozes-Ltd | RIPE | ASSIGNED PA | ● low |
| 192.117.143.0/30 | MOZES | RIPE | ASSIGNED PA | ● low |
| 213.8.57.208/29 | Mozes-Communications | RIPE | ASSIGNED PA | ● low |
| 213.8.69.208/29 | Mozes-Ltd | RIPE | ASSIGNED PA | ● low |
| 213.8.94.144/29 | Mozes-Communications | RIPE | ASSIGNED PA | ● low |
| 213.8.141.152/29 | Mozes | RIPE | ASSIGNED PA | ● low |
| 213.8.146.104/29 | Mozes | RIPE | ASSIGNED PA | ● low |
| 213.125.223.32/29 | MOZES | RIPE | ASSIGNED PA | ● low |
| 2001:41f0:342e::/48 | MOZES | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MOZES” — 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.
- MOZES_COMPUTER_COMMUNICATIONS_LTD 8 blocks
- Mozes-Computers-Communications 4 blocks
- Mozes-Nefesh 4 blocks
- Mozes-Communications-Data 1 blocks
- Mozes-Communications-Com 1 blocks
- MOZES_COMMUNICATIONS_ISRALIFE 1 blocks
- Mozes-Computers-Communication 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.
- AMOZESHVAPARVARESHGORGAN via Iran Telecommunication Company PJS sub-allocation
- AMOZESHALIGHESHM via Iran Telecommunication Company PJS sub-allocation
- MOJTAMAEAMOZESHIJAHADKESHAVARZI via Iran Telecommunication Company PJS sub-allocation
- Mozes-Communications-Data via Partner Communications Ltd. sub-allocation
- Mozes-Computers-Communication via Partner Communications Ltd. sub-allocation
- Mozes-Communications-Com via Partner Communications Ltd. sub-allocation
- MOZES_COMMUNICATIONS_ISRALIFE via Partner Communications Ltd. sub-allocation
- Amozeshi-Farhangi-Shahid-Mahdavi 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
(10 of 10)
Possible discrepancies (1)
These blocks are registered to MOZES 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.
| 2001:41f0:342e::/48 /48 | authorized for AS33915 — Vodafone Libertel B.V. |
NIC Handles
AS5486-MNT
AS9116-MNT
DUMY-RIPE
DUMY-RIPE
ZIGGO-AUTOREG1