D Commerce Bank AD

D Commerce Bank AD is a registry-only entity with no verified corporate or operational footprint beyond holding AS210992 in the RIPE NCC database. The public evidence is thin: three registry sources confirm the ASN assignment but reveal nothing about its business. If the ASN ever announces prefixes, it could affect routing tables; until then, the subject is a dormant watchpoint. Key uncertainties include whether the name represents a real bank and who controls the registry account. The profile requires monitoring of RDAP changes and BGP activity.

D Commerce Bank AD

D Commerce Bank AD is the registry holder of AS210992, an autonomous system number in the RIPE NCC region. No active routing, banking services, or corporate operations are confirmed. Its public footprint is limited to three registry sources, making it a latent infrastructure entry that could influence internet routing if it becomes operational.

Why It Matters

If AS210992 becomes active with announced prefixes, it could influence routing tables and dependency relationships for any networks that interact with it. Currently, impact is latent and tied solely to the registry record; any change to the registration or routing status would alter its infrastructure significance.

What Public Sources Show

D Commerce Bank AD is the registrant of autonomous system number AS210992 in the RIPE NCC registry. Its public footprint is limited to three registry sources: an RDAP entry, a RIPEstat page, and a Hurricane Electric BGP listing. No active network operations, banking services, or corporate website have been identified. The name suggests a financial institution, but no banking licence or regulatory filing supports that interpretation.

The only verified control point is the RIPE NCC account that manages AS210992. Whoever holds that account can modify the registry record—changing contacts, organisation details, or the aut‑num name. If the entity were to register and announce IP prefixes, it could originate BGP announcements and influence routing tables and network dependency paths. That latent capability is the sole operational lever, and for now it remains unused.

Public registry data confirms the registration. The RDAP record for AS210992 (https://rdap.org/autnum/210992) displays the aut‑num name DCOMMERCEBANK‑AS and links to the RIPE organisation ORG‑CB61‑RIPE. RIPEstat (https://stat.ripe.net/AS210992) confirms the ASN is present in the RIPE database. Hurricane Electric (https://bgp.he.net/AS210992) indexes AS210992, making it externally observable.

These three data points establish a registry identity, but nothing more. No announced IP prefixes are associated with the ASN, so it currently has no role in the global routing table.

Even an inactive ASN can become active without warning. If AS210992 starts announcing prefixes, it could suddenly appear in routing tables, altering dependency analyses for any networks that interact with it. Network operators and infrastructure analysts who map internet topology need to track such dormant registrations, because a single routing change can ripple through peering and transit relationships.

Three observable changes would alter the current assessment. First, any modification to the WHOIS/RDAP entry for AS210992—such as a new organisation name or contact—would shift the public identity of D Commerce Bank AD. Second, the first BGP announcement from AS210992 would convert the entity from latent to active, making it a live routing entity.

Third, the emergence of an official company website, banking licence, or corporate registration would help confirm the institution's legal nature and location, resolving the ambiguity of its name.

Uncertainty remains high. No independently verified official website, incorporation record, or regulator registration for D Commerce Bank AD has been located. The country of operation, headquarters address, and business scope are unconfirmed. It is unknown whether the name represents a functioning bank, a former bank, or a corporate vehicle that simply registered an ASN. Without additional evidence, the profile remains bounded by the three registry sources.

Operating Surface

D Commerce Bank AD holds an autonomous system number in the RIPE NCC registry, as shown by RDAP and BGP monitoring sources. No operational network, banking services, or corporate activity has been confirmed. Its role is limited to this registry entry, and its impact on internet infrastructure remains latent.

The subject matters because control over an autonomous system can affect internet routing visibility and dependency chains. Even a dormant ASN can become active without warning, making it a watchpoint for network operators and infrastructure analysts who need to maintain accurate dependency maps.

Watchpoints

D Commerce Bank AD is a registry-only internet number resource holder. Its strategic significance is dormant; it becomes relevant only if it activates routing. The lack of corporate backing means the ASN could be transferred, hijacked, or remain idle indefinitely. Monitoring the registration and BGP activity is the prudent stance.

Watch for changes to the AS210992 RDAP record, especially organisation name or contacts. Monitor for any BGP announcement originating from AS210992, which would signal operational activation. Seek corporate registration or banking licence records that would confirm the legal entity behind the name.

Gaps include: no corporate website, no banking licence, no physical address, no upstream or peer ASN relationships, and no public contact. The link between the name 'D Commerce Bank AD' and RIPE entity ORG-CB61-RIPE is only inferential; a directly viewable official registry page is needed.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for D Commerce Bank AD.
• RIPE registry record - RIPEstat provides a public overview page for AS210992, supporting that the ASN is publicly visible in RIPE-associated internet number resource systems.
• bgp.he.net - Public BGP intelligence services index AS210992, which can support verification that the ASN is externally observable as an internet routing entity.