VirusTotal
9 / 92 engine detections
レポートを開く“WordPress Website”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hosteurope.de.
The latest stored availability evidence still shows the domain reachable; 7 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Mastercardなりすまし: openbank.security — 未検証. 証拠の概要: VirusTotal 9/92 (BitDefender, CRDF, Fortinet, G-Data, Gridinsoft); PhishDestroy score 93/100. レジストラ…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 92 engine detections
レポートを開くSuspicious
レポートを開くScan report
レポートを開く4 community references
レポートを開く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
openbank.security is an impersonation phishing domain. Its name pairs the Openbank banking brand with a reassuring .security ending, a combination aimed at bank customers who might expect a "security check" page. PhishDestroy first flagged it on 2026-10-13. As of 2026-10-19 the domain still resolves, but its page content no longer loads.
Bank impersonation sites like this are usually reached through texts or emails claiming an account has been locked or a suspicious payment needs confirming. The victim lands on a login form styled like the real bank and enters their username, password, card details or one-time codes, which go straight to the operators. With those, criminals can log in, approve transfers or set up new devices in real time. The page title reads "WordPress Website", a generic default, while our classification is based on the impersonation of the bank name.
On 2026-10-17, 9 of 92 VirusTotal engines marked the domain as malicious, among them Kaspersky, BitDefender, Fortinet, Sophos, G-Data, Gridinsoft, CRDF and SOCRadar. That is a modest share of engines, but it comes from several unrelated vendors within days of registration. Four AlienVault OTX threat pulses also reference the domain, so other researchers have independently tracked it. Among public blocklists, it currently appears on PhishDestroy's.
The domain was registered on 2026-10-10 through Cloudflare, Inc., only three days before PhishDestroy caught it. That is the typical pattern of a short-lived phishing domain spun up for a single campaign. The site is hosted on the Host Europe GmbH network in France. It carries a free Let's Encrypt certificate, so the padlock in the browser only means the connection is encrypted. It says nothing about who runs the site.
If you entered banking details on this site, contact Openbank or your own bank through the number on your card or official app immediately. Ask them to block your card and review recent transactions. Change your online banking password and any other account that shares it. Make sure two-factor authentication is active on those accounts. Be wary of follow-up calls or messages "from the bank" asking for codes, because stolen logins are often used in exactly that kind of second-stage call. Security teams should block the domain and watch mail and SMS gateways for links to it. It is also worth monitoring for other new domains that combine bank names with .security or similar endings.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
lochlan.ns.cloudflare.comlove.ns.cloudflare.comLocation describes the IP network.
bda5b202f776c28dc0efba2dcafd2513ff7d7651f8ee2ff9ca3ac3cf9f056464Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of openbank.security · checked Oct 13, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://openbank.security/es/login.phpServer: nginxContent-Type: text/html; charset=UTF-8X-Powered-By: PHP/8.4.26Cache-Control: no-store, no-cache, must-revalidateno-store, no-cache, must-revalidatekeep-alivetext/html; charset=UTF-8Tue, 13 Oct 2026 10:59:46 GMTThu, 19 Nov 1981 08:52:00 GMTno-cachenginxchunkedPHP/8.4.26Values retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
到達可能
No threat flag
View source9/92 engine detections
View source4 community references
View sourcePD-20261013-F4A1B8
Page captured
View sourceopenbank.security
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
openbank.security
PD-20261013-F4A1B8 Recipient: abuse@hosteurope.de AUP & Terms of Service Violations: Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices. Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension. Applicable Legal Framework (DE): German Criminal Code § 263 (Fraud) German Criminal Code § 263a (Computer Fraud) Telemedia Act (TMG) German law prohibits fraud and computer-based deception. Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
openbank.security)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.