Yonko Draganov is a public intelligence profile built from public registry sources. It summarizes what can be verified about the subject—a technical contact for AS210299—separates public infrastructure facts from unsupported claims, and outlines the evidence boundary. The main value is tracking contact continuity; a change would signal operational movement. Data gaps include the absence of employer, location, and any independent biographical confirmation.
The public role is limited to a 'tech' contact designation in internet number resource registries. No evidence supports a wider operational or decision-making scope, and the contact serves as a publicly visible coordination point rather than an ownership or leadership signal.
Tracking is warranted because a named contact in ASN registries provides a public signal for operational continuity. Any change in that registration can indicate administrative or organizational shifts within the network operator that uses AS210299, even when the operator itself is not publicly identified.
Tracking is warranted because a named contact in ASN registries provides a public signal for operational continuity. Any change in that registration can indicate administrative or organizational shifts within the network operator that uses AS210299, even when the operator itself is not publicly identified.
The public role is limited to a 'tech' contact designation in internet number resource registries. No evidence supports a wider operational or decision-making scope, and the contact serves as a publicly visible coordination point rather than an ownership or leadership signal.
If Yonko Draganov remains consistently listed as the technical contact for AS210299, the public record maintains a stable linkage that analysts can use for infrastructure monitoring. Removal, replacement, or discovery of a corporate affiliation would immediately raise or lower the subject's relevance and could signal operational realignments.
Yonko Draganov is a public intelligence profile built from public registry sources. It summarizes what can be verified about the subject—a technical contact for AS210299—separates public infrastructure facts from unsupported claims, and outlines the evidence boundary. The main value is tracking contact continuity; a change would signal operational movement. Data gaps include the absence of employer, location, and any independent biographical confirmation.
If Yonko Draganov remains consistently listed as the technical contact for AS210299, the public record maintains a stable linkage that analysts can use for infrastructure monitoring. Removal, replacement, or discovery of a corporate affiliation would immediately raise or lower the subject's relevance and could signal operational realignments.
| 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
Yonko Draganov
Yonko Draganov is a person name listed as a technical contact in public RIPE and RDAP registry records for autonomous system AS210299. The profile is bounded by registry evidence; no employer, executive authority, or operational control is confirmed.
Why It Matters
If Yonko Draganov remains consistently listed as the technical contact for AS210299, the public record maintains a stable linkage that analysts can use for infrastructure monitoring. Removal, replacement, or discovery of a corporate affiliation would immediately raise or lower the subject's relevance and could signal operational realignments.
What Public Sources Show
Yonko Draganov appears in public RIPE and RDAP registry records as the technical contact for autonomous system AS210299, using the handle YD1063-RIPE. The publicly available evidence supports no broader claim about employer, executive authority, or operational control. This profile stays inside what the registry documents show.
When a named contact is tied to an ASN registration, it provides a stable public signal for operational coordination. Continuity in that listing suggests administrative stability; removal or replacement can indicate a shift in the organization behind the network. For infrastructure analysts, tracking that contact is a low-cost way to detect possible administrative changes in AS210299.
The RDAP record at rdap.org/autnum/210299 lists Yonko Draganov with the role “tech.” The RIPE Database query for YD1063-RIPE confirms the same handle and role. Neither source attaches a company name, physical address, or telephone number. No active IP prefixes are visible in the current evidence, so the operational footprint beyond the ASN itself is unknown.
The authority surface is narrow—limited to appearing as a registry contact. There is no public proof that Yonko Draganov can make routing decisions, allocate resources, or represent an organization. The contact serves as a publicly listed point for technical inquiries, not as an indication of ownership or leadership.
All facts derive from two registry sources. There is no independent biographical confirmation, no employment record, and no corporate website linking Yonko Draganov to an employer. The role could be outdated or inactive. Without an active prefix announcement, the significance of the contact is modest.
Analysts should monitor the registry record for any change: removal of the name, replacement by another contact, or addition of an organization field. A new PeeringDB entry, a company website, or an announced IP prefix for AS210299 would strengthen the assessment. Discovery of an employer would transform the profile from a thin registry entry into an actionable intelligence lead.
The main value is in contact continuity. A stable listing is a neutral indicator; a change warrants investigation. The public evidence does not justify claims about business influence or network control. Instead, Yonko Draganov functions as a registry reference point that can signal movement in the otherwise opaque operator behind AS210299.
Operating Surface
The public role is limited to a 'tech' contact designation in internet number resource registries. No evidence supports a wider operational or decision-making scope, and the contact serves as a publicly visible coordination point rather than an ownership or leadership signal.
Tracking is warranted because a named contact in ASN registries provides a public signal for operational continuity. Any change in that registration can indicate administrative or organizational shifts within the network operator that uses AS210299, even when the operator itself is not publicly identified.
Watchpoints
The subject represents a thin registry signal. Its intelligence value depends entirely on persistence as a contact; any change is a higher-signal event than continuity. The absence of prefix data limits operational context.
Registry deltas (removal, replacement, new org field), new routing evidence, employer discovery, and active prefix announcements for AS210299 would change the assessment.
Lack of second independent identity source, employer name, active prefix or PeeringDB record, and biographical confirmation. A corporate affiliation would transform the profile.
Sources
- Registry RDAP / WHOIS record - Provides identity and registry context linking Yonko Draganov to AS210299.
- RIPE registry record - Verifies RIPE handle YD1063-RIPE and 'tech' role for Yonko Draganov.
Domain of operation
Yonko Draganov is a person name listed as a technical contact in public RIPE and RDAP registry records for autonomous system AS210299. The profile is bounded by registry evidence; no employer, executive authority, or operational control is confirmed.
- Registry RDAP / WHOIS record: Provides identity and registry context linking Yonko Draganov to AS210299. Evidence basis: source-4eb43dac4362
Timeline
- Yonko Draganov public evidence observed
Tracking is warranted because a named contact in ASN registries provides a public signal for operational continuity. Any change in that registration can indicate administrative or organizational shifts within the network operator that uses AS210299, even when the operator itself is not publicly identified.
At A Glance
- Name: Yonko Draganov
- Type: Individual registry-holder label
- Base: Global
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- source-backed relationship updates
Why It Matters
- If Yonko Draganov remains consistently listed as the technical contact for AS210299, the public record maintains a stable linkage that analysts can use for infrastructure monitoring. Removal, replacement, or discovery of a corporate affiliation would immediately raise or lower the subject's relevance and could signal operational realignments.
- 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.
If Yonko Draganov remains consistently listed as the technical contact for AS210299, the public record maintains a stable linkage that analysts can use for infrastructure monitoring. Removal, replacement, or discovery of a corporate affiliation would immediately raise or lower the subject's relevance and could signal operational realignments.
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
If Yonko Draganov remains consistently listed as the technical contact for AS210299, the public record maintains a stable linkage that analysts can use for infrastructure monitoring. Removal, replacement, or discovery of a corporate affiliation would immediately raise or lower the subject's relevance and could signal operational realignments.
Watchpoints
- The subject represents a thin registry signal.
- Its intelligence value depends entirely on persistence as a contact; any change is a higher-signal event than continuity.
- The absence of prefix data limits operational context.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Yonko Draganov?
Tracking is warranted because a named contact in ASN registries provides a public signal for operational continuity. Any change in that registration can indicate administrative or organizational shifts within the network operator that uses AS210299, even when the operator itself is not publicly identified.
What evidence supports the profile?
Provides identity and registry context linking Yonko Draganov to AS210299.
What should readers watch next?
The subject represents a thin registry signal.
