KASPERSKY-LAB
BGP inherited
Cluster stats
Netblocks7
All fragments 128 blocks across 5 clusters
Cluster ID193004151
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-06

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.122.169.0/26 KASPERSKY-LAB RIPE ASSIGNED PA ● low
212.73.221.192/27 KASPERSKY-LAB RIPE ASSIGNED PA ● low
212.162.49.128/26 KASPERSKY-LAB RIPE ASSIGNED PA ● low
212.248.32.224/28 Kaspersky_Lab RIPE ASSIGNED PA ● low
2001:728:1401::/64 Kaspersky-Lab-NET RIPE ASSIGNED ● low
2001:4c08:2008::/48 KASPERSKY-LAB RIPE ASSIGNED ● low
2a00:2381:868::/48 KASPERSKY-LAB RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
42.9% of checked blocks have valid RPKI ROA coverage (3 of 7)
Possible discrepancies (2)

These blocks are registered to KASPERSKY-LAB but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2001:4c08:2008::/48 /48 authorized for AS3356 — Level 3 Parent, LLC
2a00:2381:868::/48 /48 authorized for AS2856 — British Telecommunications PLC

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE LEVEL3-MNT MAINT-VIPAR MTU-NOC