Mohamad Chehimi is a person listed in RIPE registry records as the administrative and technical contact for AS210318. The evidence is limited to official RDAP and RIPE Database records, confirming the entity handle MC45897-RIPE but providing no employer, biography, or prefix data. The profile establishes a monitoring baseline this contact point; changes in the registry or any routing activity from AS210318 would alter the operational significance. Key uncertainties include record staleness and whether Chehimi is a current, active contact or a historical role account.

Mohamad Chehimi

Mohamad Chehimi is an administrative and technical contact for autonomous system 210318 in RIPE registry records. His listing provides a public point of contact for coordination, though no operational control, employer, or active routing footprint is verified by the available evidence.

Why It Matters

If AS210318 becomes active, Chehimi’s contact role would influence how quickly and with whom external parties coordinate during outages, hijacks, or disputes. Currently, the lack of BGP activity limits the immediate operational impact to a regulatory trail, but any change would raise his significance.

What Public Sources Show

Mohamad Chehimi is listed in the RIPE Database as the administrative and technical contact for autonomous system 210318. He uses the entity handle MC45897-RIPE, which ties his name to the autonomous system’s registration. This public record makes him a contact point for coordination, abuse handling, or resource management queries tied to AS210318.

Two official sources provide the foundation: the RDAP data at rdap.org/autnum/210318, and the RIPE Database query for MC45897-RIPE. IANA’s RDAP bootstrap framework enables these lookups, positioning Chehimi within the internet’s operational metadata layer. No first-party company website, PeeringDB profile, or social media documentation corroborates his role or current employment. The evidence therefore supports a narrow registry-contact profile.

Chehimi’s operational surface is limited to the registry listing itself. There is no prefix ownership data, and the autonomous system has no observable BGP announcements in the current evidence set. AS210318 appears dormant from a routing perspective. Should it become active—announcing prefixes or engaging in BGP—Chehimi’s contact details would become operationally material for incident response, peering, or abuse handling.

The RIPE record for MC45897-RIPE does not include an organization field, so the network operator behind AS210318 remains undisclosed. Chehimi may represent an unlisted entity, or the handle could be a role account rather than a personal name. Without a corporate website, network map, or professional biography, the connection between the name and any real-world operating entity stays unverified.

It is not possible to confirm whether Chehimi is a current, active contact or a historical entry. No employer, nationality, or city of residence is verified by the limited records. The name appears in no other supplied sources besides the RIPE registry. This absence of independent biographical data means the person behind the handle cannot be independently verified, and the listing could be outdated or maintainer-managed.

Watchpoints that would alter the assessment include any modification to the MC45897-RIPE object—such as a new organization reference, changed contact details, or removal of Chehimi’s name. The appearance of BGP announcements from AS210318 would immediately raise Chehimi’s infrastructure relevance. Discovery of a professional profile, employer, or industry event linking Chehimi to AS210318 would bridge the gap between registry listing and operational context.

Operating Surface

Publicly accessible RDAP data for aut-num 210318 lists Mohamad Chehimi through entity handle MC45897-RIPE with admin and tech contact roles, indicating a network-operations contact context within RIPE-managed Internet number resource records. No other operating context is verified by the provided evidence.

Changes to the registry record for AS210318 or the entity handle MC45897-RIPE could shift the contact point for routing issues, abuse reports, or resource management. Tracking Chehimi’s continued presence in public registry data helps analysts understand who operators and authorities might reach for coordination, even if the AS is not currently routing.

Watchpoints

Mohamad Chehimi represents a registry contact point with no operational footprint, so the strategic priority is low. However, if AS210318 becomes active, Chehimi’s contact becomes a lever for engagement. Monitoring registry changes is the primary method to detect shifts in control or affiliation.

Monitor MC45897-RIPE for organization association changes or contact removal. Also track BGP for AS210318; any announcements increase operational significance.

Lack of employer, organization, and routing data. Need to verify if Chehimi is a role account or active person. Additional public sources like company registries, LinkedIn, or network operator community lists would strengthen assessment.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Mohamad Chehimi.
• RIPE registry record - RIPE Database search provides a public registry page for entity handle MC45897-RIPE, the handle associated with Mohamad Chehimi in the provided RDAP-derived material.
• Registry RDAP / WHOIS record - IANA publishes the RDAP bootstrap framework used by public RDAP clients such as rdap.org to resolve registry records for Internet number resources.