Autonomous system
AS51038 HCL
Unclassified RIPE
Summary
Hospices Civils de Lyon
hospital business france healthcare
HCL is the autonomous system for Hospices Civils de Lyon.
What it's used for
- The space carries internal hospital infrastructure, evidenced by the reverse DNS record
checked.hcl.frand the netnameHCL. - The AS announces 512 IPv4 addresses within a single /23 prefix and 1 IPv6 prefix, with 3 observed neighbours, indicating a small, self-contained internal network rather than a transit or access provider.
- Traffic from this AS consists of internal communications, clinical systems, and administrative endpoints for the hospital network.
Notable
- Registrants include
FranceIX Admin,Hospices civils de Lyon, andREZOPOLE HOSTMASTER, aligning with the holder identity. - The address inventory is compact, consisting of one IPv4 block and one IPv6 block, typical of a single-site corporate or institutional estate.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-16, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 512 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| FR | France | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS51038- Registry name
- HCL
- Registrant
- MNT-LYONIX
- Abuse contact
- abuse@rezopole.net
- Registered
- 2010-05-20
- Last changed
- 2023-10-04
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Hospices civils de Lyon
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Website
- https://www.chu-lyon.fr
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 4 valid, 0 with no ROA
- ROAs
- 2 authorising AS51038
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 4 naming AS51038
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,783 prefixes, as published 2026-10-17. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere