The jixiaoyun-admin handle is a RIPE role label that serves as a contact for AS215062, which is registered to the dissolved UK company STAINCLOUD LTD. The artifact persists after dissolution with a valid RPKI ROA, but no active BGP routing is confirmed. The core risk is misattribution: analysts may mistake the handle for an active institution. Uncertainty centres on who controls the RIPE credentials. Watchpoints include changes to WHOIS, ROA expiry, and any live BGP announcements.
The subject operates as a contact pointer within RIPE's registration database, granting no independent legal or operational status. It appears in WHOIS and RDAP records for AS215062, but every public source identifies STAINCLOUD LTD—now dissolved—as the actual number resource holder. The handle's only observable function is to identify administrative and technical contacts for that ASN.
Because registry role labels can be misread as institutional signals, jixiaoyun-admin must be tracked as a phantom entity. Its continued appearance in routing security records (RPKI) and the lack of live BGP verification mean that network operators and investigators could build false dependency maps or trust assumptions around a dissolved company. The valid ROA raises questions about who, if anyone, controls the number resources.
Because registry role labels can be misread as institutional signals, jixiaoyun-admin must be tracked as a phantom entity. Its continued appearance in routing security records (RPKI) and the lack of live BGP verification mean that network operators and investigators could build false dependency maps or trust assumptions around a dissolved company. The valid ROA raises questions about who, if anyone, controls the number resources.
The subject operates as a contact pointer within RIPE's registration database, granting no independent legal or operational status. It appears in WHOIS and RDAP records for AS215062, but every public source identifies STAINCLOUD LTD—now dissolved—as the actual number resource holder. The handle's only observable function is to identify administrative and technical contacts for that ASN.
The main impact is misattribution of operational authority. Analysts may treat the handle as an active organization, leading to incorrect routing policy, threat classification, or commercial risk assessment. The presence of a valid RPKI ROA after company dissolution suggests that either automated processes are still running or that an individual retains credentials to assert routing authority, which could be leveraged for accidental or malicious route hijacking if misconfigured.
The jixiaoyun-admin handle is a RIPE role label that serves as a contact for AS215062, which is registered to the dissolved UK company STAINCLOUD LTD. The artifact persists after dissolution with a valid RPKI ROA, but no active BGP routing is confirmed. The core risk is misattribution: analysts may mistake the handle for an active institution. Uncertainty centres on who controls the RIPE credentials. Watchpoints include changes to WHOIS, ROA expiry, and any live BGP announcements.
The main impact is misattribution of operational authority. Analysts may treat the handle as an active organization, leading to incorrect routing policy, threat classification, or commercial risk assessment. The presence of a valid RPKI ROA after company dissolution suggests that either automated processes are still running or that an individual retains credentials to assert routing authority, which could be leveraged for accidental or malicious route hijacking if misconfigured.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
jixiaoyun-admin
jixiaoyun-admin is a RIPE WHOIS role handle (JA10488-RIPE) that functions as an administrative and technical contact for autonomous system 215062. All public evidence ties that ASN to STAINCLOUD LTD, a UK company dissolved in August 2025. The handle persists with an active RPKI route origin authorization, creating a material attribution hazard for analysts who mistake the label for an operating entity.
Why It Matters
The main impact is misattribution of operational authority. Analysts may treat the handle as an active organization, leading to incorrect routing policy, threat classification, or commercial risk assessment. The presence of a valid RPKI ROA after company dissolution suggests that either automated processes are still running or that an individual retains credentials to assert routing authority, which could be leveraged for accidental or malicious route hijacking if misconfigured.
What Public Sources Show
The identifier jixiaoyun-admin is not a company, institution, or person. It is a RIPE database role object—specifically, the handle JA10488-RIPE—that serves as a technical and administrative contact for autonomous system number 215062. Analysts frequently mistake such registry handles for active operating entities, but all verifiable corporate registration and asset authority points to a dissolved UK firm, STAINCLOUD LTD.
The persistence of this handle after the company’s legal demise creates a material attribution hazard.
Public WHOIS records list AS215062 under the name STAINCLOUD-LTD, with organization identifier ORG-SL1292-RIPE. The resource was created in April 2024 and last modified in December 2024. Commercial IP intelligence platforms like IPinfo map the ASN to STAINCLOUD LTD, classifying it as inactive with no detected peering or IP ranges.
Meanwhile, the UK Companies House registry shows STAINCLOUD LTD was incorporated on 28 February 2024 but dissolved via compulsory strike-off on 5 August 2025—after the last WHOIS modification date.
The material risk is twofold. First, the handle’s continued appearance in WHOIS and routing security records enables a non-existent legal entity to masquerade as a network operator, misdirecting threat intelligence and due diligence. Second, a valid Route Origin Authorization (ROA) exists for the prefix 2a0f:85c1:3c7::/48 under AS215062.
Issued through RIPE’s RPKI, the ROA is valid from July 2025 through July 2026—meaning someone retains the cryptographic credentials to authorize routing announcements, though the listed company no longer exists.
The handle itself operates no infrastructure. Its entire control surface is the RIPE NCC account that manages the ASN and RPKI objects. No public source identifies the real individuals behind those credentials. VPS forum ads describe a “StainCloud” brand offering KVM and GPU servers with German hosting and ruble pricing, but no confirmed link ties those ads to the current state of AS215062.
The administrative role is strictly a registry pointer, not an operational one.
Key uncertainty surrounds the absence of live BGP data. IPinfo reports no active routes for AS215062, and the ROA may be a remnant of automated creation or expired infrastructure. Without route-table evidence, we cannot confirm whether any traffic originates from the prefix. The handle could be reassigned by RIPE NCC without notice, or the ROA could expire.
Until the RIPE account holder is known, the handle is not a trustworthy control indicator.
Readers should monitor for WHOIS record modifications for JA10488-RIPE or AS215062. The expiry of the ROA in July 2026 will test whether the resource has an active custodian. Any new BGP announcements from AS215062, especially involving the authorized prefix, would signal operational activity. Re-registration or restoration of STAINCLOUD LTD at Companies House would alter the legal status.
Finally, connection of the handle to any known threat campaigns or routing incidents would escalate its significance.
Operating Surface
The subject operates as a contact pointer within RIPE's registration database, granting no independent legal or operational status. It appears in WHOIS and RDAP records for AS215062, but every public source identifies STAINCLOUD LTD—now dissolved—as the actual number resource holder. The handle's only observable function is to identify administrative and technical contacts for that ASN.
Because registry role labels can be misread as institutional signals, jixiaoyun-admin must be tracked as a phantom entity. Its continued appearance in routing security records (RPKI) and the lack of live BGP verification mean that network operators and investigators could build false dependency maps or trust assumptions around a dissolved company. The valid ROA raises questions about who, if anyone, controls the number resources.
Watchpoints
The handle is a phantom entity resulting from incomplete lifecycle management of Internet number resources. Its continued existence creates a gap between legal reality and routing security posture. Network intelligence consumers should treat the handle as a non-indicator of organizational activity and instead focus on the actual controller of the RIPE credentials.
Monitor for any changes in WHOIS entries for JA10488-RIPE or AS215062. Watch for BGP announcements from the associated prefix. The expiry of the ROA on 2026-07-24 will test whether the resource is actively managed. Any new corporate filing for STAINCLOUD LTD or reassignment of the ASN would alter the assessment.
Live BGP table data is needed to confirm whether the prefix is currently announced. The identity of the RIPE account holder behind JA10488-RIPE is unknown. Direct RDAP verification is pending. Fiscal or service ownership records do not exist for the handle itself.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for jixiaoyun-admin.
- Registry RDAP / WHOIS record - RIPE WHOIS mirror data identifies AS215062 as STAINCLOUD-LTD, linked to ORG-SL1292-RIPE, with ASSIGNED status, STAINCLOUD LTD address data, creation on 22 April 2024 and last modification on 18 December 2024.
- ipinfo.io - Commercial ASN dataset identifies AS215062 as STAINCLOUD LTD, website staincloud.com, country United Kingdom, registry RIPE, and labels it inactive with no known IP ranges or peering data in that dataset.
- find-and-update.company-information.service.gov.uk - Official company registry identifies STAINCLOUD LTD as company number 15530558, incorporated on 28 February 2024, with registered office at 27 Old Gloucester Street, London, and SIC 63110 for data processing, hosting and related activities.
- find-and-update.company-information.service.gov.uk - Official filing history records first Gazette notice for compulsory strike off on 20 May 2025 and final Gazette dissolved via compulsory strike off on 5 August 2025.
- console.rpki-client.org - Public RPKI validator output shows a route origin authorization for AS215062 covering 2a0f:85c1:3c7::/48, validation OK, valid from 25 July 2025 until 24 July 2026.
- poiskvps.ru - Hosting directory and discussion page list StainCloud as a KVM VPS host with Germany listed as service country, ruble pricing, five tariffs, and StainCloud account replies about fair use and support issues.
- zenno.club - Forum posting attributed to a StainCloud account advertises StainCloud.com VPS or VDS servers, dedicated servers, GPU servers, 1 Gbps ports and multiple payment methods. This is useful as service surface evidence, not as corporate registry proof.
Domain of operation
jixiaoyun-admin is a RIPE WHOIS role handle (JA10488-RIPE) that functions as an administrative and technical contact for autonomous system 215062. All public evidence ties that ASN to STAINCLOUD LTD, a UK company dissolved in August 2025. The handle persists with an active RPKI route origin authorization, creating a material attribution hazard for analysts who mistake the label for an operating entity.
- Registry RDAP / WHOIS record: public-source identity and registry context for jixiaoyun-admin. Evidence basis: source-8624c9117cec
Timeline
- jixiaoyun-admin public evidence observed
Because registry role labels can be misread as institutional signals, jixiaoyun-admin must be tracked as a phantom entity. Its continued appearance in routing security records (RPKI) and the lack of live BGP verification mean that network operators and investigators could build false dependency maps or trust assumptions around a dissolved company. The valid ROA raises questions about who, if anyone, controls the number resources.
At A Glance
- Name: jixiaoyun-admin
- Type: Digital infrastructure institution
- Base: Europe
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- source-backed relationship updates
Why It Matters
- The main impact is misattribution of operational authority. Analysts may treat the handle as an active organization, leading to incorrect routing policy, threat classification, or commercial risk assessment. The presence of a valid RPKI ROA after company dissolution suggests that either automated processes are still running or that an individual retains credentials to assert routing authority, which could be leveraged for accidental or malicious route hijacking if misconfigured.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
The main impact is misattribution of operational authority. Analysts may treat the handle as an active organization, leading to incorrect routing policy, threat classification, or commercial risk assessment. The presence of a valid RPKI ROA after company dissolution suggests that either automated processes are still running or that an individual retains credentials to assert routing authority, which could be leveraged for accidental or malicious route hijacking if misconfigured.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
The main impact is misattribution of operational authority. Analysts may treat the handle as an active organization, leading to incorrect routing policy, threat classification, or commercial risk assessment. The presence of a valid RPKI ROA after company dissolution suggests that either automated processes are still running or that an individual retains credentials to assert routing authority, which could be leveraged for accidental or malicious route hijacking if misconfigured.
Watchpoints
- The handle is a phantom entity resulting from incomplete lifecycle management of Internet number resources.
- Its continued existence creates a gap between legal reality and routing security posture.
- Network intelligence consumers should treat the handle as a non-indicator of organizational activity and instead focus on the actual controller of the RIPE credentials.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track jixiaoyun-admin?
Because registry role labels can be misread as institutional signals, jixiaoyun-admin must be tracked as a phantom entity. Its continued appearance in routing security records (RPKI) and the lack of live BGP verification mean that network operators and investigators could build false dependency maps or trust assumptions around a dissolved company. The valid ROA raises questions about who, if anyone, controls the number resources.
What evidence supports the profile?
public-source identity and registry context for jixiaoyun-admin.
What should readers watch next?
The handle is a phantom entity resulting from incomplete lifecycle management of Internet number resources.






