DESEM Desem Turizm ve Ticaret Limited Sirketi

DESEM Desem Turizm ve Ticaret Limited Sirketi is a Turkish travel agency pulled into internet infrastructure intelligence through its appearance in AS199531 aggregator records. The profile confirms the company’s real-world travel-sector identity from official tourism member lists but leaves the ASN link as contested routing evidence because no authoritative RIPE source, first-party website, or PeeringDB profile verifies operational network control. Watchpoints center on primary registry reconciliation, prefix activity, and first-party network disclosures. The case is a practical demonstration of secondary ASN directory fragility and the risk of misattribution when registry metadata is stale or mirrored incorrectly.

DESEM Desem Turizm ve Ticaret Limited Sirketi

DESEM Desem Turizm ve Ticaret Limited Sirketi is a Turkish travel agency whose name appears in public routing aggregators linked to AS199531, but the association is not confirmed by primary registry data. The profile explains the company's real-world identity, the contested internet footprint, and the watchpoints that could resolve the ambiguity.

Why It Matters

Analysts using this profile should treat AS199531 as routing evidence attached to DESEM’s name, not as confirmed infrastructure control. A genuine ASN link would make prefix announcements, withdrawals, or measurement changes meaningful; a stale attribution would mean that associating network events with DESEM could misdirect investigations, due diligence, and dependency mapping. The evidence boundary forces explicit uncertainty until a RIPE primary source reconciles the attribution.

What Public Sources Show

DESEM Desem Turizm ve Ticaret Limited Sirketi is a travel agency based in Turkey that has surfaced in a very different context: internet routing intelligence. Its name appears repeatedly in public datasets linked to Autonomous System AS199531, a small internet routing identifier. Yet no authoritative source confirms that the travel company actually operates this network resource.

This ambiguity makes DESEM an instructive case in the fragility of secondary ASN directories and the risks of misattribution.

The company’s real-world identity is not in doubt. Turkey’s official tourism-sector member lists maintained by TURSAB and TURSAV both record DESEM alongside Herbie Tourism & Travel Agency. These listings, including a regional election document, establish DESEM as a genuine travel-sector entity. That concrete identity stands in contrast to the contested internet footprint.

On the internet side, multiple BGP measurement platforms—Cloudflare Radar, BGP.he.net, CIDR Report, and IPGeolocation—consistently label AS199531 with DESEM’s name and place it in Turkey, reporting a single IPv4 prefix and little activity. Yet a direct AS199531 record from IPGeolocation contradicts this by assigning the same autonomous system to an individual in Spain, with zero routes.

The inconsistency across secondary sources underlines the central problem: none of these aggregators is a primary registry.

If the association between DESEM and AS199531 is genuine, any change in route announcements or withdrawals could affect reachability analysis for networks depending on that prefix. However, if the linkage is stale or mirrored in error—as the conflicting record suggests—analysts who treat network events as actions of the travel agency risk misdirecting investigations, due diligence, and threat intelligence.

The main risk is not operational failure but corrupted trust in the mapping itself.

The current evidence base lacks the items that would resolve the attribution. No direct RIPE Database record linking DESEM to AS199531 was confirmed from a current RIPE page. The company has no known website, PeeringDB profile, or first-party network disclosure. Financial, ownership, and contact details are absent. Cloudflare Radar itself reports limited public evidence data for quality and adoption metrics on AS199531, further reducing operational interpretability.

Several concrete developments could change the assessment. A primary registry record, such as a RIPE or WHOIS entry, that explicitly names DESEM would solidify the link. The appearance of new prefixes or significant traffic on AS199531 would increase its infrastructure relevance. Conversely, a correction or update from the secondary platforms that removes the DESEM name would eliminate the ambiguity.

Until then, the case remains a watchpoint for directory fragility and the need for primary-source verification.

Operating Surface

DESEM Turizm ve Ticaret Limited Sirketi is publicly visible as a Turkey-linked travel-agency legal entity listed alongside Herbie Tourism in tourism-sector member directories. In internet operations, the same name surfaces in multiple AS199531 aggregator records, but the ASN record should be treated as contested routing evidence rather than as the company identity itself.

DESEM matters because public sources join a real travel-agency company to a small internet-routing footprint. If the company controls or depends on AS199531, changes in ASN attribution, route visibility, or measurement status can affect reachability analysis, vendor or customer due diligence, and security investigations.

If the ASN mapping is stale or conflicting, the main impact is misattribution risk: analysts could wrongly attach infrastructure behavior to the travel-agency company without resolving the registry record.

Watchpoints

The DESEM case illustrates how a non-infrastructure entity can appear in network intelligence feeds solely through stale or conflicting secondary records. Strategically, this warns BTW analysts to validate ASN-to-organization mappings against primary RIR data before incorporating them into risk or dependency models. The ambiguous link also serves as a low-cost live test for assessing the consistency of public BGP measurement platforms.

1. Primary RIPE Database AS199531 record update that names or removes DESEM. 2) New prefix announcements or BGP activity on AS199531. 3) First-party website or network disclosure from DESEM. 4) Changes in the conflicting IPGeolocation record. 5) Any PeeringDB entry for AS199531.

Missing: direct RIPE Database entity for AS199531 referencing DESEM; official company website; PeeringDB profile; verified upstream providers; financial or ownership records; any operational metrics beyond one reported prefix. These gaps make it impossible to confirm whether DESEM actually operates AS199531 or if the name is a directory artifact.

Sources

• Internet registry record - public-source identity and registry context for DESEM Desem Turizm ve Ticaret Limited Sirketi.
• tursav.org - Lists DESEM TURIZM VE TIC. LTD. STI. together with HERBIE TOURISM & TRAVEL AGENCY in a public tourism-sector member list.
• tursab.org.tr - Lists entry 2993 as HERBIE TOURISM AND TRAVEL AGENCY and DESEM TURIZM VE TIC.LTD.STI. in the Orta Anadolu regional election-list PDF.
• radar.cloudflare.com - Identifies AS199531 as Desem Turizm ve Ticaret Limited Sirketi and places it in Turkey; the page also reports unavailable or limited public evidence quality metrics for this AS.
• radar.cloudflare.com - Identifies AS199531 as Desem Turizm ve Ticaret Limited Sirketi in Turkey while reporting limited public evidence data for several adoption and protocol metrics.
• bgp.he.net - Lists AS199531 in Turkey as Desem Turizm ve Ticaret Limited Sirketi with a small visible route footprint in the country table.
• cidr-report.org - Lists AS199531 as DESEM or Desem Turizm ve Ticaret Limited Sirketi, Turkey, in a one-prefix current BGP aggregation report.
• ipgeolocation.io - Lists AS199531 in the Turkey ASN country page as Desem Turizm ve Ticaret Limited Sirketi with one IPv4 route and zero IPv6 routes in the reviewed summary.
• ipgeolocation.io - Shows a conflicting direct AS199531 record mapping the ASN to Francisco Jose Ruiz Diaz, carbonet, Spain, and zero routes, which conflicts with current DESEM Turkey routing-directory results.