VirusTotal
5 / 92 engine detections
レポートを開く“BlackOps Guide — Bridge & Transport Guide”
ブロックリスト掲載ドメイン: blackops.guide — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 92 engine detections
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く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
blackops.guide is an impersonation phishing page that presents itself as "BlackOps Guide — Bridge & Transport Guide." PhishDestroy first flagged it on 2026-09-05. As of 2026-10-19 the site is still online and serving content, so anyone landing on it today sees the live page. The page title describes a bridge and transport guide, while our classification is impersonation phishing.
Impersonation pages borrow the look and language of a service people already trust, then use that trust to get visitors to act. A "bridge guide" framing suits users who are trying to move assets between networks and are actively looking for instructions. Pages like this typically steer readers to enter login details, recovery information or wallet connections through controls the attacker runs. Whatever the visitor submits goes straight to the operators, and they can use it to take over accounts or empty funds.
On 2026-10-19, VirusTotal showed 5 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a modest count, but five unrelated vendors reaching the same verdict is a meaningful signal for a site that is still live. The domain also appears in 4 AlienVault OTX threat pulses. On the blocklist side, PhishDestroy currently lists it.
The domain was registered on 2026-07-09 through Fewmoretaps OU d/b/a Trustname.com, 58 days before PhishDestroy detected it. That gap suggests the domain was set up ahead of time rather than registered and used on the same day. The site sits behind Cloudflare's network in the US, which hides the server that actually hosts the content. Its TLS certificate comes from Google Trust Services (WE1), so the browser padlock only confirms an encrypted connection. It says nothing about whether the site is legitimate.
Do not follow any instructions on this page. If you typed a password there, change it right away wherever you reuse it and turn on app-based two-factor authentication. If you connected a wallet or signed anything while following its bridge steps, revoke the approvals you granted and move your funds to a fresh wallet. Never give anyone your seed phrase. For defenders, block blackops.guide at DNS and proxy level, report it to Cloudflare and the registrar, and add it to your phishing filters while it remains active.
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.
Edge-IP の評判はこのドメインに起因しません。
aldo.ns.cloudflare.comeva.ns.cloudflare.comLocation describes the IP network.
14ad25b97e7585c3be16c5eec0201f8c7962c0fcd32cef7eec234f7b9b55667aSaved 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 blackops.guide · checked Sep 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.
blackops.guide
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
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
2→3
到達可能
5/92 engine detections
View source4 community references
View sourceNo threat flag
View sourceblackops.guide
View sourcePage captured
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 ↗
blackops.guide)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.