Core Entity Brief
| Entity | Alexis Lurot |
|---|---|
| Public role | 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. |
| Region | RIPE NCC Service Region |
| Category | Individual registry-holder label |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | QUARTER_30_120D |
| Impact | Medium |
| Confidence | 0.95 |
| Evidence coverage | 1 public source reference |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 03, 2026 |
The organization that holds autonomous system AS210349 is an entity in the RIPE NCC region; its corporate identity, business model, and operational reach are not disclosed in the available evidence.
What It Does
- Autonomous system operator: The organization administers AS210349, which suggests it exchanges internet traffic with other networks. Its revenue likely comes from providing connectivity, hosting, or other internet services, but no specific services, customers, or revenue model can be verified.
- Registry dependency: Like any network operator, the organization's ability to coordinate with peers, respond to abuse reports, and maintain routing security depends on accurate and responsive WHOIS contacts.
Operating Snapshot
- ASN registration: AS210349 is registered in the RIPE NCC service region. The current RDAP record lists Alexis Lurot as the admin/tech contact. No BGP routing footprint, traffic volumes, or network scale information is included in the evidence set.
- Contact accuracy: The only visible proxy for the organization's operational posture is the accuracy of its registry contacts. Stale or outdated information could indicate broader governance or staffing issues within the organization.
Control Surface
- RIPE NCC account: Modifications to the ASN record and associated objects (such as route objects or RPKI ROAs) require authentication through the RIPE NCC portal. The handle AL20664-RIPE is the current public control point for such changes.
- Public RDAP query: Anyone can access the registry record; if the contact information is inaccurate, the organization's ability to coordinate with the broader internet community is weakened.
Watchpoints
- Company identification: If a company name, website, or other identifying information is later linked to AS210349, the operational assessment could change significantly. Currently, the entity operating the ASN is opaque.
- Contact accuracy: A sudden change in the admin/tech contacts for AS210349 could indicate internal reorganization, acquisition, or a security incident. Monitoring the RDAP record is essential to detect such shifts.

