VirusTotal
17 / 89 engine detections
レポートを開く“ClickFix — Управление файлами”
認証情報フィッシング: verify-cloud.digital — コンテンツが利用できません (HTTP 404). 証拠の概要: VirusTotal 17/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Dr.Web); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 89 engine detections
レポートを開くSuspicious
レポートを開く7 community references
レポートを開く80/100
レポートを開く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
This domain, verify-cloud.digital, was registered on July 25, 2026 through Fewmoretaps OU doing business as Trustname.com. The registration is recent and the domain resolves to the IPv4 address 86.109.75.161, which is served by the anycast name servers ns1.anycastdns.cz and ns2.anycastdns.cz. Within a day of creation the domain appeared on a security blocklist and is currently listed by PhishDestroy, indicating that threat‑intel feeds have observed malicious use. VirusTotal has processed the domain with 91 scanning engines; none have raised a detection at the time of analysis, but the lack of a positive result does not constitute confirmation of benign behavior.
No public SSL certificate information, HTTP response codes, page title, or Safe Browsing verdict are available, so the surface‑web characteristics remain unverified. The limited evidence points to a credential‑phishing campaign, as indicated by the threat type classification, but the exact lure, target brand, or phishing kit cannot be confirmed without content inspection. Defenders should proactively block resolve‑to IP 86.109.75.161 and add verify-cloud.digital to domain‑allow‑list exclusions.
Monitoring of DNS queries for the domain and its name servers is advised, as is periodic re‑scanning with VirusTotal or other sandbox services to detect any later payloads. Network intrusion detection signatures that flag HTTP traffic to the IP or TLS handshakes with the domain should be deployed. Because the domain is still active, continuous threat‑intel correlation is recommended to capture any future attribution or victim reports.
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.
ns1.anycastdns.czns2.anycastdns.czLocation describes the IP network.
66ea9599fb2737b287728ab3ba3da282792ec82b8080cc4d8001f12edadba950www.verify-cloud.digitalSaved 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.verify-cloud.digitalDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of verify-cloud.digital · checked Jul 30, 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.
http_other: raw=http_404; http=404; via=http_proxy; server=cloudflare
verify-cloud.digital
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
到達可能→利用不可
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
到達可能
7 community references
View source17/89 engine detections
View sourcePage captured
View sourceNo threat flag
View sourceverify-cloud.digital
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 ↗
verify-cloud.digital)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.