Commerce Bank is a Bulgarian bank appearing in RIPE registry records as the abuse contact for AS210992. No active BGP prefixes are observed, limiting its operational profile to the registry entry. Evidence includes the RDAP record, SWIFT BIC directory, and the bank's website. The exact legal name and the employment status of named contacts remain unverified. Key watchpoints are record changes and routing emergence.
Commerce Bank serves as the publicly listed abuse contact for AS210992, which means external parties will direct network abuse reports and technical inquiries related to that autonomous system to the bank. Because AS210992 carries no active prefix announcements in public observation, the role is limited to a registry-based contact function rather than active routing operations.
The bank's presence in the RIPE registry creates a dependency for network operators who may need to reach the responsible party for AS210992. If the registry record is accurate, it correctly routes incident reports; if it is stale or inaccurate, misdirected communications could cause delays. Tracking this subject helps analysts maintain an up-to-date picture of who handles network operations for this autonomous system.
The bank's presence in the RIPE registry creates a dependency for network operators who may need to reach the responsible party for AS210992. If the registry record is accurate, it correctly routes incident reports; if it is stale or inaccurate, misdirected communications could cause delays. Tracking this subject helps analysts maintain an up-to-date picture of who handles network operations for this autonomous system.
Commerce Bank serves as the publicly listed abuse contact for AS210992, which means external parties will direct network abuse reports and technical inquiries related to that autonomous system to the bank. Because AS210992 carries no active prefix announcements in public observation, the role is limited to a registry-based contact function rather than active routing operations.
Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active participant in internet routing rather than a passive registry contact.
Commerce Bank is a Bulgarian bank appearing in RIPE registry records as the abuse contact for AS210992. No active BGP prefixes are observed, limiting its operational profile to the registry entry. Evidence includes the RDAP record, SWIFT BIC directory, and the bank's website. The exact legal name and the employment status of named contacts remain unverified. Key watchpoints are record changes and routing emergence.
Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active participant in internet routing rather than a passive registry contact.
| 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
Commerce Bank
Commerce Bank是一家位于索非亚的保加利亚银行，在RIPE注册记录中作为自治系统AS210992（自治系统名称DBANK）的组织滥用联系人出现。该机构没有观察到BGP路由活动，因此其互联网基础设施足迹最小，但其注册记录成为需要联系该自治系统责任方的任何网络运营商的主要信号。 另见: Dcent Investments BV.
为什么重要
AS210992的RDAP记录过时或发生更改，将改变公共联系途径，可能导致滥用报告发送到过时或不正确的目的地。如果AS210992开始宣告BGP前缀，该银行的基础设施相关性将上升，使其成为互联网路由的积极参与者，而不仅仅是被动的注册联系人。 另见: VoltzzNode Enterprise SRL.
公共来源显示的内容
Commerce Bank是一家位于索非亚的保加利亚银行，在公共互联网注册记录中作为自治系统AS210992（使用名称DBANK）的组织滥用联系人出现。该银行是通过其SWIFT BIC列表和公司网站验证的合法金融机构，但由于没有从该ASN观察到活动的BGP前缀宣告，其在网络基础设施中的角色仅限于该注册条目。 另见: mioso Verwaltungs GmbH.
公共来源包括AS210992的RIPE RDAP记录，其中将Commerce Bank列为滥用联系人，并带有一个基于域的邮箱。RIPEstat ASN概览确认该条目存在，而SWIFT BIC目录列出了索非亚的“Commerce Bank AD”。该银行自己的网站dbank.bg与注册域名相匹配。这些记录共同建立了一个一致但定义狭窄的公共身份。
作为注册的滥用联系人，Commerce Bank是涉及AS210992的网络滥用报告和技术查询的指定接收方。然而，由于该自治系统没有宣告任何BGP前缀，该银行目前不参与互联网路由。因此，控制面仅限于更新注册记录和管理相关域的能力，而不是操作网络硬件或进行对等互联。 另见: GLOBALTRUST SRL.
如果注册数据是最新的，外部运营商将正确地将查询路由到银行，从而促进事件响应。过时或不准确的数据可能会误导这些通信，可能延迟补救或将问题归因于错误的一方。注册记录的更改或路由活动的开始将直接改变基础设施观察者评估银行参与程度的方式。 另见: Pronect Technology LTD.
关键观察点包括对AS210992的RDAP或WHOIS记录的任何修改，这将改变公共联系基线。来自AS210992的BGP前缀宣告的出现将表明实时路由操作，并提高银行的基础设施重要性。通过保加利亚官方公司注册条目解决“Commerce Bank”与“Commerce Bank AD”之间的法律名称差异，将加强身份图景。 另见: Alexis Lurot.
缺乏保加利亚公司注册或银行监管机构记录意味着精确的法律名称和注册细节尚未得到独立确认。两名指定联系人——Bisser Hadjimarkov和Stoyan Stoyanov——的雇佣状况不明；他们可能是银行员工或外部代表。该银行的内部网络基础设施仍然不透明，如果银行激活AS210992，其运营相关性可能会发生变化。 另见: PG 软件技术有限公司.
Commerce Bank的概况是一个基于注册表的快照。它为监控分配给保加利亚金融机构的互联网号码资源的分析师提供了一个起点，但它并未描述一个活跃的网络运营商。最重要的信号是记录变化和路由活动，其中任何一种都需要重新评估该对象的基础设施相关性。
操作面
Commerce Bank作为AS210992的公开列出滥用联系人，这意味着外部方将与该自治系统相关的网络滥用报告和技术查询指向该银行。由于AS210992在公共观察中没有活动前缀宣告，该角色仅限于基于注册表的联系功能，而不是活动路由操作。
该银行在RIPE注册表中的存在，为可能需要联系AS210992责任方的网络运营商创造了依赖性。如果注册记录准确，它将正确路由事件报告；如果记录过时或不准确，错误的通信可能会导致延迟。跟踪此对象有助于分析师保持对谁负责该自治系统网络操作的最新认识。
观察点
Commerce Bank的注册条目代表一个休眠的号码资源，如果被激活，将把保加利亚金融机构与活动互联网路由联系起来。跟踪它有助于为可能需要联系责任方的网络运营商进行依赖性映射。
AS210992的RDAP/WHOIS记录的修改、BGP宣告的启动，以及通过保加利亚公司注册解决法律名称差异。
没有保加利亚公司注册或银行监管机构记录确认法律名称和注册。指定联系人与银行的雇佣关系未知。缺乏BGP宣告使得网络足迹未经确认。
来源
- 注册表RDAP / WHOIS记录 - Commerce Bank的公共来源身份和注册表上下文。
- RIPE注册记录 - RIPEstat为AS210992提供公共参考页面，支持该ASN存在于RIPE相关的公共互联网号码资源数据中。
- swift.com - 公共SWIFT BIC目录将DEMIBGSF列为COMMERCE BANK AD，位于保加利亚索非亚，支持存在一家使用英文名称Commerce Bank的保加利亚银行。
- 运营商网站 - 公共网站dbank.bg展示了银行的公司网络存在，并与公布的滥用联系人详情中使用的域一致。
Domain of operation
Commerce Bank is a Sofia-based Bulgarian bank that appears in RIPE registry records as the organisational abuse contact for autonomous system AS210992 (autonomous system name DBANK). The institution has no observed BGP routing activity, keeping its internet infrastructure footprint minimal but making its registry record the primary signal for any network operator who needs to contact the party responsible for that autonomous system.
- Registry RDAP / WHOIS record: public-source identity and registry context for Commerce Bank. Evidence basis: source-fdd9f3852612
Timeline
- Commerce Bank public evidence observed
The bank's presence in the RIPE registry creates a dependency for network operators who may need to reach the responsible party for AS210992. If the registry record is accurate, it correctly routes incident reports; if it is stale or inaccurate, misdirected communications could cause delays. Tracking this subject helps analysts maintain an up-to-date picture of who handles network operations for this autonomous system.
At A Glance
- Name: Commerce Bank
- Type: Digital infrastructure institution
- Base: Bulgaria
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- documented relationships updates
Why It Matters
- Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active participant in internet routing rather than a passive registry contact.
- 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.
Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active participant in internet routing rather than a passive registry contact.
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
Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active participant in internet routing rather than a passive registry contact.
Watchpoints
- Commerce Bank's registry entry represents a dormant number resource that, if activated, would link a Bulgarian financial institution to active internet routing.
- Tracking it supports dependency mapping for network operators who may need to contact the responsible party.
- Modifications to AS210992's RDAP/WHOIS records, initiation of BGP announcements, and resolution of the legal name discrepancy through a Bulgarian corporate registry.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Commerce Bank?
The bank's presence in the RIPE registry creates a dependency for network operators who may need to reach the responsible party for AS210992. If the registry record is accurate, it correctly routes incident reports; if it is stale or inaccurate, misdirected communications could cause delays. Tracking this subject helps analysts maintain an up-to-date picture of who handles network operations for this autonomous system.
What evidence supports the profile?
public-source identity and registry context for Commerce Bank.
What should readers watch next?
Commerce Bank's registry entry represents a dormant number resource that, if activated, would link a Bulgarian financial institution to active internet routing.
