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.
Auteurj.liu@btw.media
Editorial owner accountable for this profile route.
Temps de lecture3 min
Estimated reading time at standard editorial pace.
Publié leMay 26, 2026
Date this profile last entered editorial circulation.
Last updateJun 03, 2026
Date this profile last entered editorial circulation.
CategoryIndividual registry-holder label
Controlled classification used for cross-profile comparison.
RégionGlobal
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
Type de contenuProfile
Structured profile used for cross-category comparison.
Domaine principalInfrastructure
Primary editorial domain framing the analysis.
SujetPublic network contact
Controlled taxonomy label used for this profile route.
HorizonQUARTER_30_120D
Most likely window for strategy or governance effects.
ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confiance0.95
Anchored to multiple primary-source references and direct disclosures.
Dossier de preuves
Sources primaires utilisées pour la classification et l'évaluation d'impact.
Kenneth B. Mc Cleaft is the sole contact for dormant AS212010 per RIPE RDAP. No employer or routing footprint. If AS212010 activates, his registry authority could affect prefix routing. Main risks: record staleness, unknown affiliation, no corroboration. Watch for RDAP changes, BGP announcements, and organizational disclosure.
Core Entity Brief
Core Entity Brief
Entity
Kenneth B. Mc Cleaft
Public role
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.
Region
Global
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 entity associated with Kenneth B. Mc Cleaft in public registry records is an individual contact point for AS212010, not a commercial company; its operating role is limited to registry administration of the autonomous system.
What It Does
Registry stewardship: The ‘business model’ is non-commercial: the entity exists as a designated maintainer of the AS212010 registry object. It does not sell services, earn revenue, or support customers. The value it provides is purely administrative, ensuring the ASN record remains accurate and compliant with RIPE NCC policy.
No commercial operation: No supplied evidence indicates any commercial transactions, service offerings, or customer relationships. The entity is not registered as a company, has no known website or product portfolio, and does not appear in any marketplace.
Operating Snapshot
Registry footprint: The only verifiable operating footprint is the RDAP entry for AS212010, which lists Mr. Mc Cleaft as admin and tech contact with handle KBMC1-RIPE. The ASN is allocated but has no observed BGP announcements, PeeringDB presence, or internet service infrastructure.
Contact capability: In principle, the entity acts as the communication endpoint for registry-related queries about AS212010. However, there is no public evidence of any such interactions occurring, nor of the entity proactively managing network operations.
Control Surface
Registry object management: The entity controls the RIPE database aut-num object for AS212010 and any linked maintainer, allowing it to update contact details, change authorization credentials, and create or modify route objects. This control is analogous to ownership of the ASN’s public registration identity.
Indirect routing influence: By creating or withdrawing route objects, the entity can influence how BGP speakers treat prefixes originated by AS212010 (e.g., for RPKI validation). Since no active routing is observed, this influence is currently theoretical.
Watchpoints
Registry mutability: Because the entity’s entire operating surface is the registry record, any alteration—especially to contact or maintainer fields—is a significant event that could indicate a change in control, ownership, or operational intent.
ASN activation: If AS212010 begins announcing prefixes, the entity’s control surface becomes operationally critical, and its timely management of RPKI ROAs and route objects will directly affect routing security. This warrants technical monitoring.
Organizational affiliation: Discovery of a parent organization or employer would shift the entity’s profile from a standalone registry contact to a representative of a larger entity, introducing commercial and jurisdictional dimensions.
Domain of operation
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.
Public role: Kenneth B. Mc Cleaft is framed by 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. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record
Operating surface: Public network contact and Global provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record
Timeline
Kenneth B. Mc Cleaft public profile updated
Public coverage records Kenneth B. Mc Cleaft as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: 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.
Object role: In public registry records, he serves as the admin and tech contact for AS212010, a role that allows him to modify the aut-num object, manage maintainer references, and create route objects. The ASN has no known routing announcements, so his role is dormant from an operational perspective.
Impact note: If AS212010 begins originating BGP announcements, Mr. Mc Cleaft’s control over route objects 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.
Control surface: public operating records, official service pages, source-backed relationship updates
Key dependencies: official company sources, public registries, operator-published records
Public View
The public read of Kenneth B. Mc Cleaft is limited to visible role, operating context, and relationship evidence.
Watchpoints
New public role, affiliation, product, policy, or market disclosures.
Verified relationship changes involving named organizations or people.
Caveats
Private or unverified claims are excluded from this public view.
FAQ
Why is Kenneth B. Mc Cleaft included?
Kenneth B. Mc Cleaft has public evidence that makes the institution relevant to BTW's coverage of digital infrastructure, governance, or markets.
What is public about this profile?
The public layer covers visible role, operating context, linked organizations, and evidence-backed watchpoints.
What should readers watch next?
Readers should watch for source-backed role changes, new partnerships, regulatory exposure, operating expansion, or evidence that changes the public assessment.
