Kenneth B. Mc Cleaft
Kenneth B. Mc Cleaft is the administrative and technical contact for AS212010 according to RIPE NCC RDAP. No employer or active BGP footprint is observed; his authority over the registry entity gives him latent control over route and RPKI entities, but the record’s staleness and the ASN’s inactivity make his current operational role uncertain.
Why It Matters
If AS212010 begins originating BGP announcements, Mr. Mc Cleaft’s control over route entities and RPKI-related entries would influence whether its prefixes are accepted by other networks—potentially causing reachability issues or security incidents. Until then, his impact is latent, and the primary risk is that the registry record is stale, obscuring who truly controls the ASN.
What Sources Show
Kenneth B. Mc Cleaft is the administrative and technical contact for Autonomous System 212010, as recorded in the RIPE NCC’s public RDAP database. The registration names him under the handle KBMC1-RIPE and assigns him authority over the ASN’s registry entity. No other public evidence confirms his employment, organizational affiliation, or active network operations. His profile today is a narrow registry snapshot with latent infrastructure implications.
The sole supporting source is the RDAP response for AS212010, an official registry record. It lists Mr. Mc Cleaft as both admin and tech contact, roles that permit updates to the ASN’s aut-num entity, maintainer references, and route entities. However, the ASN currently has no observed BGP announcements, PeeringDB presence, or known internet services.
The record’s last update date is not observed in supplied public sources, raising uncertainty about its freshness and the accuracy of the contact information.
If AS212010 begins originating IP prefixes, Mr. Mc Cleaft’s registry authority would become operationally material. He would control the creation and withdrawal of route entities, which in turn affects how other networks accept or reject those prefixes. He could also manage RPKI-related entities, directly influencing routing security. Until routing commences, this authority is theoretical and may be subject to stale credentials or delegated responsibilities.
The absence of any employer, professional biography, or organization disclosure leaves his motivation and accountability unestablished. He could be a private individual holding the ASN for personal or legacy purposes, or he could act on behalf of an undisclosed entity. Without a public trail, the registry role alone cannot confirm his engagement with internet infrastructure. This gap limits the assessment to a dormant contact point rather than an active operator.
Changes to the RDAP record—new contact fields, added maintainer, or an organization reference—would signal a shift in control or intent. The first BGP announcement from AS212010 would be the most pivotal event, testing whether the registration remains operational. Analysts should watch for public documents linking Mr. Mc Cleaft to a specific network operator, which would contextualize his role.
Until such evidence appears, the profile stands as a registry indicator, not a verdict on active authority.
Operating Surface
In public registry records, he serves as the admin and tech contact for AS212010, a role that allows him to modify the aut-num entity, manage maintainer references, and create route entities. The ASN has no known routing announcements, so his role is dormant from an operational perspective.
Kenneth B. Mc Cleaft is tracked because his registry-granted authority over AS212010 could directly affect IP prefix routing and RPKI validation if the ASN becomes active. Currently, the ASN is inactive and his profile is limited to a lone RDAP record, but any activation or record change would make this subject materially relevant to routing security.
Watchpoints
This subject represents a low-cost intelligence target: a single registry entry pointing to a dormant ASN. The true value is in monitoring for activation, which would convert a paper contact into an operational routing decision-maker. Without employer context, the subject could be a personal legacy ASN or an abandoned registration.
Concrete watchpoints: (1) any update to AS212010’s RDAP record, especially contact or maintainer changes; (2) BGP announcements originating from AS212010, which would immediately elevate the subject’s relevance; (3) public disclosure of an employer or organization linking Mr. Mc Cleaft to a network operator, providing accountability context.
The data gap is severe: no employer, no biography, no routing, no PeeringDB, and no timestamp for the RDAP contact record. Without a second source, the registry entry alone cannot confirm current control, reachability, or intent. Additional sources such as a company website, staff listing, or a BGP routing snapshot would close critical gaps.
Sources
- Registry RDAP / WHOIS record - The RDAP record names Kenneth B. Mc Cleaft as the admin and tech contact for AS212010 with handle KBMC1-RIPE.
