Alexis Lurot

Alexis Lurot is the admin and tech contact for AS210349 (handle AL20664-RIPE). The sole evidence is the RIPE NCC RDAP record. The affiliated organization is not named, and there is no independent confirmation of current employment or routing authority. The profile must be treated as a registry snapshot that could be outdated. Watchpoints include changes to the handle or ASN, and appearance of the handle on other networks.

Alexis Lurot

Alexis Lurot is listed as the administrative and technical contact for autonomous system AS210349 in the RIPE NCC registry, with the handle AL20664-RIPE. The publicly available RDAP record is the sole piece of evidence, and no employer, biography, or routing footprint is available.

Why It Matters

If the contact record turns out to be outdated, the entity operating AS210349 may become unreachable for critical operational notifications, abuse complaints, and legal inquiries, which could erode trust in the network and delay incident response across the internet.

What Sources Show

Alexis Lurot is the administrative and technical contact for autonomous system AS210349, as recorded in the RIPE NCC registry under the handle AL20664-RIPE. The sole public evidence for this role is the RDAP query at https://rdap.org/autnum/210349, which lists him in both admin and tech capacities. This profile is limited to what the registry directly shows; no employer, biography, or routing footprint is currently available.

As the named contact, Lurot has the authority to modify the public WHOIS entry for AS210349, including technical contact details, routing policy references, and potentially RPKI trust anchor information. This is a trust-based function: only representatives authorized by the ASN holder should hold such a handle. However, the registry role does not by itself confirm current employment or confer control over actual router configurations or peering decisions.

Accurate registry contacts are critical for internet operational coordination. If the WHOIS data for AS210349 becomes stale—for example, because Lurot has left the associated organization—network operators, abuse teams, and law enforcement may be unable to reach a responsive party during routing incidents, spam campaigns, or legal inquiries. That delay could enable malicious activity to persist and erode trust in the network.

The sole source of information is the RIPE NCC RDAP record, an official registry entry that is publicly queryable. The record does not disclose the legal name of the organization holding AS210349, nor does it provide any professional details about Lurot. No independent verification—such as a company website, social media profile, or BGP routing data—is included in the current evidence set.

Several important gaps remain. It is not possible to determine whether Lurot is currently employed by the ASN holder, what his job title might be, or whether he has any authority over routing decisions. The registry entry could be historical or purely administrative. Without first-party confirmation, this profile must be treated as a snapshot that may not reflect the present reality.

Readers monitoring this subject should watch for changes to the RDAP record. If the AL20664-RIPE handle is removed from AS210349 or replaced, Lurot’s association with the autonomous system ends. Transfers, routing policy updates, or RPKI modifications involving the ASN could also signal shifts in his operational relevance.

The appearance of the same handle on additional networks or organizations would indicate a broader role, but such expansion would need new registry evidence to confirm.

For now, Alexis Lurot remains a single point of contact in the internet’s registry layer. Understanding his role and its limitations helps analysts calibrate the risk associated with AS210349 and highlights the importance of keeping registry data current. Until further evidence emerges, the profile serves as a reference for operational monitoring rather than a definitive biographical record.

Operating Surface

As the admin and tech contact for AS210349, Alexis Lurot has the ability to modify the public WHOIS record, including contact details, routing policy references, and RPKI trust anchor information. This role signals that the ASN holder has entrusted him with administrative functions, but it does not necessarily confer control over actual router configurations or peering decisions.

Accurate WHOIS contacts are essential for internet coordination; if the registry data for AS210349 becomes stale, network operators, abuse teams, and law enforcement may be delayed in reaching the right party during incidents, potentially allowing harmful activity to continue. Monitoring this contact helps assess the operational posture of the associated autonomous system.

Watchpoints

The listing of Alexis Lurot as the sole admin/tech contact for AS210349 suggests he is a gatekeeper for registry changes and abuse correspondence for that autonomous system. Because the registry holder is opaque, any change to this contact could signal organizational restructuring, acquisition, or loss of operational control.

Monitor the RIPE NCC RDAP record for AS210349 at least monthly. Watch for removal or replacement of the AL20664-RIPE handle, addition of new contacts, transfers of the ASN, or changes in associated maintainer entities.

The legal name of the AS210349 holder, current employment and title of Alexis Lurot, BGP routing footprint of the ASN, any first-party biography or employer website, and proof that the registry role reflects current reality.

Sources

• RIPE NCC RDAP record for AS210349 - The RIPE NCC RDAP record for AS210349 lists Alexis Lurot as administrative and technical contact with handle AL20664-RIPE.