Etisalcom

ETISALCOM
Data as of 2026-11-15
Registry
This organisation
Netblocks8 · 1,537 IPv4 addresses
IPv6 1 prefix (largest 2001:1a40:10::a503:5457:1/128)
Also registered under this name 42 netblocks across 2 separate records
Record ID270487447
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.69.248.29/32 Etisalcom PEERINGDB ASSIGNED ● high
2001:1a40:10::a503:5457:1/128 Etisalcom PEERINGDB ASSIGNED ● high
80.95.208.0/24 ETISALCOM RIPE ASSIGNED PA ● low
80.95.209.0/24 ETISALCOM RIPE ASSIGNED PA ● low
80.95.210.0/24 ETISALCOM RIPE ASSIGNED PA ● low
80.95.211.0/24 ETISALCOM RIPE ASSIGNED PA ● low
80.95.212.0/24 ETISALCOM RIPE ASSIGNED PA ● low
80.95.213.0/24 ETISALCOM RIPE ASSIGNED PA ● low

IPv6 ranges (1)

Footprint over time

21 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-11-15

Network trust

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

NIC Handles

AS35457 DUMY-RIPE DUMY-RIPE MNT-ETISALCOMNET