VirusTotal
10 / 92 engine detections
打开报告“403 Forbidden”
冒充 Ankr: glbalmritbk.pro — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 10/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); PhishDestroy…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
10 / 92 engine detections
打开报告3 community references
打开报告Scan report
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
glbalmritbk.pro is an impersonation phishing site. It is built to pass itself off as a legitimate service so visitors trust it with sensitive information. PhishDestroy first flagged it on 2026-10-04. On 2026-10-19 it was still online, with its content behind access protection. Its browser title reads "403 Forbidden," while we classify the domain as an impersonation phishing page.
An impersonation page copies the look, wording and branding of a service people already use, then waits for them to arrive through links in messages, ads or search results. The visitor believes they are on the real site and types in usernames, passwords, one-time codes, personal details or payment information. All of it goes to the operators, who use it to take over accounts or commit fraud. The squeezed, vowel-dropped domain name is the kind meant to slip past a quick glance at the address bar.
On 2026-10-07, VirusTotal showed 10 of 92 security engines flagging the domain. The vendors included alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That share is not overwhelming, but these are well-known engines that reached the same verdict independently. The domain also appears in three AlienVault OTX threat pulses, and it is listed on the PhishDestroy blocklist.
The domain was registered on 2026-09-30 through TuringSign Inc. d/b/a Cosmotown, only four days before PhishDestroy detected it. That short gap fits a site set up for quick use before blocklists catch it. It is hosted in the United States on the Aquiryn LLC network at 23.153.104.17. Its free Let's Encrypt certificate gives it a padlock icon, which shows the connection is encrypted but says nothing about who runs the site.
If you entered a password on glbalmritbk.pro, change it right away on the genuine service and on every other account that uses the same password. Turn on two-factor authentication everywhere you can. If you shared card or bank details, call your bank, ask to block the card and watch for unfamiliar charges. Be wary of follow-up messages that cite what you typed, because operators often reuse stolen data for targeted scams. Security teams should block the domain and its hosting IP at the DNS, proxy and email layers, and search their logs for any users who reached it.
ns8.my-control-panel.comglbalmritbk.propriority 0Location describes the IP network.
4a7cf3db8c2adfc0d78d462db13489eb314aa2337ae1d0e6e71e859fc6ee46d5www.app.glbalmritbk.proSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.app.glbalmritbk.proDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of glbalmritbk.pro · checked Oct 5, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
captcha: raw=captcha; http=200; via=https_proxy; server=LiteSpeed
glbalmritbk.pro
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→protected
captcha · challenge
protected→live_content
content_served
未知→protected
captcha · challenge
未知→protected
captcha · challenge
protected→live_content
content_served
未知→protected
captcha · challenge
未知→protected
captcha · challenge
未知→protected
captcha · challenge
protected→live_content
content_served
未知→protected
captcha · challenge
未知→protected
captcha · challenge
live_content→protected
captcha · challenge
未知→live_content
content_served
protected→live_content
content_served
未知→protected
captcha · challenge
未知→protected
captcha · challenge
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
No threat flag
View source10/92 engine detections
View source3 community references
View sourceglbalmritbk.pro
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
glbalmritbk.pro)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.