viphost

Data as of 2026-10-04
Registry
This organisation
Netblocks4
IPv6 3 prefixes (largest 2a14:4f80::/38)
Also registered under this name 5 netblocks across 2 separate records
Record ID246684244
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 5 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 (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
217.117.29.64/26 VIPHOST RIPE ASSIGNED PA ● low
2a0d:5000:2::/48 VIPHOST RIPE ASSIGNED ● low
2a14:4f80::/38 viphost RIPE ALLOCATED-BY-LIR ● low
2a14:4f85::/38 viphost RIPE ALLOCATED-BY-LIR ● low

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (4 of 4)
Possible discrepancies (3)

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

2a14:4f80::/38 /38 authorized for AS49556 — Web Dadeh Paydar Co (Ltd)
2a14:4f85::/38 /38 authorized for AS216054 — Taymaz Gostaran Naghshe Almas Co. ( Ltd )
2a0d:5000:2::/48 /48 authorized for AS15440 — UAB "Baltnetos komunikacijos"

NIC Handles

BNK-LT-MNT DUMY-RIPE DUMY-RIPE lir-ir-amir-1-MNT lir-ir-taymaaz-1-MNT