SENIMENG-NET

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks10
Record ID245617479
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 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 (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
88.79.95.112/28 SENIMENG-NET RIPE ASSIGNED PA ● low
88.79.119.120/29 SENIMENG-NET RIPE ASSIGNED PA ● low
88.79.119.216/29 SENIMENG-NET RIPE ASSIGNED PA ● low
88.79.161.200/29 SENIMENG-NET RIPE ASSIGNED PA ● low
88.79.161.216/29 SENIMENG-NET RIPE ASSIGNED PA ● low
88.79.178.80/29 SENIMENG-NET RIPE ASSIGNED PA ● low
88.79.180.216/29 SENIMENG-NET RIPE ASSIGNED PA ● low
176.95.38.56/29 SENIMENG-NET RIPE ASSIGNED PA ● low
178.15.152.40/29 SENIMENG-NET RIPE ASSIGNED PA ● low
178.15.209.144/28 SENIMENG-NET RIPE ASSIGNED PA ● low

Footprint over time

15 weekly snapshots · JSON
10 +2 netblocks since 2026-07-05
2026-07-05 peak 10 2026-10-04

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

ARCOR-MNT DUMY-RIPE DUMY-RIPE