セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
openbank.security favicon

openbank.security

“WordPress Website”

レジストラ
Cloudflare
Resolved IP
92.205.19.135
Registered
2026年10月10日
PhishDestroy assessment クリティカル
First observed Oct 13, 2026 10:59 UTC · PhishDestroy
VirusTotal 検出数: 9/92 自動ブランドラベル:Mastercard 若いドメイン: 10 日経過
OTX: 4 refs 2026年10月13日 1 Report Sent
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 9。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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.

Elapsed since first report
7 days
Reports sent
1
Latest case ID
PD-20261013-F4A1B8
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
レポート概要

Mastercardなりすまし: openbank.security — 未検証. 証拠の概要: VirusTotal 9/92 (BitDefender, CRDF, Fortinet, G-Data, Gridinsoft); PhishDestroy score 93/100. レジストラ…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 9 / 92 · OTX 4 references 6 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

クリティカル
VirusTotal
9 / 92
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

保存済みキャプチャ · 3 captures

Observed page title
WordPress Website
Automated brand references
Mastercard Santander Visa
TLS証明書
発行者 Let's Encrypt / YR2 · stored validity ends in 79 days

Domain details

ドメイン
URLScan verdict 分析完了 score 0 report ↗
IPレピュテーション abuse score 0/100 0 reports checked 2026年10月13日
OTX tags 2026-10activeall-domainsblocklistcontentcryptoドメインdrainerfraudlivemonthlyphishdestroyphishingscam
レジストラ Cloudflare DE(DE)
不正利用連絡先abuse@hosteurope.de
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年10月10日 (10d · Very New!) — Expires 2027年10月10日
技術詳細Provenance & timestamps
初確認2026年10月13日
DOM Analysisanalyzed 2026年10月13日score 93/1003 brand signals
Submitted URLhttps://openbank.security/es/login.php
Favicon Hash
ケース ID
ICANN OVERSIGHT

認定と RAA の背景

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft 自動送信は一切行われません。

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
92.205.19.135
Network ASN
AS21499
Organization
GD MASS Network
Observed location
Strasbourg, FR
Server header
nginx

ネームサーバー 2

  • lochlan.ns.cloudflare.com
  • love.ns.cloudflare.com

Location describes the IP network.

TLS証明書

Issuer
Let's Encrypt / YR2
Valid from
2026-10-10 13:07:25
Valid until
2027-01-08 13:07:24
Validity
Within stored validity dates
Collection time
2026-10-13 13:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbda5b202f776c28dc0efba2dcafd2513ff7d7651f8ee2ff9ca3ac3cf9f056464

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

脅威情報の照合 · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
使用技術 · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

9 / 92 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
BitDefender
CRDF
Fortinet
G-Data
Gridinsoft
カスペルスキー
SOCRadar
ソフォス
VIPRE

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of openbank.security · checked Oct 13, 2026

100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.05s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.45s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://openbank.security/es/login.php
対応
HTTP 200
HTML body
72 B
Compressed
87 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/8.4.26
Cache-Control: no-store, no-cache, must-revalidate
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Cache-Control
no-store, no-cache, must-revalidate
Connection
keep-alive
Content-Type
text/html; charset=UTF-8
Date
Tue, 13 Oct 2026 10:59:46 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Pragma
no-cache
Server
nginx
Transfer-Encoding
chunked
X-Powered-By
PHP/8.4.26

Values retained by the collector; long values may be shortened during collection.

Registration & observation details2

Availability observations

Last reachable observation
Last content observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    不明→live_content

    content_served

  2. Availability monitor · First collection record

    到達可能

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    9/92 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Abuse report sent

    PD-20261013-F4A1B8

    abuse@hosteurope.de
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    openbank.security

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

openbank.security

証拠および外部報告書

送信済み証拠のスナップショット
Sent: Ledger records: 1 Case ID: PD-20261013-F4A1B8 Recipient: abuse@hosteurope.de
PDF notice generated Notice text archived (800 chars)
Abuse notice text as sent to the provider
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.
詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

6 evidence signal groups linked 1 stored notification records 未検証
If credentials were compromised, report immediately. Do not engage with recovery scammers.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

Template-based draft · optional AI wording assistance requires separate consent

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

FBIのガイドライン

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) openbank.security)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/embed/domain/openbank.security"
  title="PhishDestroy threat report for openbank.security"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>