Dassault

Registry
Cluster stats
Netblocks9
Registered in Netherlands (3) · France (2) · Sweden (2) · Greece (1)
All fragments 182 blocks across 15 clusters
Cluster ID205150432
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-13

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.95.15.216/29 DASSAULT-NET RIPE ASSIGNED PA ● low
84.96.12.12/30 DASSAULT RIPE ASSIGNED PA ● low
84.96.13.0/30 DASSAULT RIPE ASSIGNED PA ● low
195.97.89.156/30 DASSAULT RIPE ASSIGNED PA ● low
195.242.53.120/29 DASSAULT-SE RIPE ASSIGNED PA ● low
212.83.216.208/29 Dassault RIPE ASSIGNED PA ● low
212.83.232.224/29 Dassault RIPE ASSIGNED PA ● low
213.207.91.160/29 Dassault RIPE ASSIGNED PA ● low
2001:4018:1000:33::/64 Dassault RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Dassault” — 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.
Combined view of all 15 name-family clusters →
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.

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS9150-MNT DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT PANAFON-MNT SE-UUNET-MNT TDC-SE-MNT