LTC-HOME
Cluster stats
| Netblocks | 24 |
| All fragments | 25 blocks across 2 clusters |
| Cluster ID | 192087897 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (24)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 78.84.0.0/17 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 78.84.128.1 – 78.84.255.255 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.0.0/19 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.32.0/21 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.44.0/22 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.48.0/21 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.72.0/24 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.90.0/23 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.96.0 – 81.198.115.255 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.128.0/19 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.176.0/22 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.197.0 – 81.198.207.255 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.216.0/21 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 81.198.224.0/19 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 84.237.128.0/18 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 84.237.196.0 – 84.237.203.255 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 84.237.204.0 – 84.237.209.255 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 84.237.248.0/22 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 84.237.252.0/23 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 84.237.254.0/24 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 87.110.0.0/17 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 87.110.160.0/20 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 195.13.233.0/24 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
| 195.114.48.0/20 | LTC-HOME | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(24 of 24)
RPKI-inferred operator
SIA Tet
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
LTK