VirusTotal
9 / 89 engine detections
レポートを開く“Speccy — Advanced Hardware Profiler & Live Thermal Tracker”
フィッシング: speccy.software — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 9/89 (alphaMountain.ai, Chong Lua Dao, CRDF, CyRadar, Forcepoint ThreatSeeker); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 89 engine detections
レポートを開く6 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
Analysis of the domain speccy.software indicates a confirmed phishing campaign targeting users seeking hardware diagnostic utilities. The domain, registered on May 26, 2026, through Spaceship, Inc., resolves to 104.21.26.174 (AS13335, Cloudflare, Inc., US) and remains active as of July 12, 2026. The page title, 'Speccy — Advanced Hardware Profiler & Live Thermal Tracker,' suggests an attempt to impersonate a legitimate system monitoring tool, though the exact content and delivery mechanism of the phishing payload have not been fully analyzed. Infrastructure analysis reveals the use of Cloudflare nameservers (harvey.ns.cloudflare.com, ruth.ns.cloudflare.com) and a Let's Encrypt SSL certificate (E8), which are common in both legitimate and malicious deployments. Detection data shows the domain is flagged by three security blocklists, including PhishDestroy and MetaMask, and appears in one AlienVault OTX threat intelligence pulse. Gridinsoft assigns a trust score of 0/100, reinforcing its high-risk classification. While only one of ninety-one security vendors on VirusTotal currently flags the domain, this does not diminish its confirmed malicious status, as phishing domains often evade initial detection. The domain employs multiple technologies, including jsDelivr, HSTS, Google Analytics, and Cloudflare Browser Insights, which may be used to enhance credibility, track victims, or obfuscate malicious activity. The registrar, Spaceship, Inc., has been associated with other high-risk domains, though no direct attribution to a specific threat actor or group is available at this time. Defenders should treat this domain as actively malicious and prioritize blocking or monitoring traffic to 104.21.26.174 and related Cloudflare IP ranges. Further investigation into victim interactions and payload delivery is recommended to determine the full scope of the campaign.
Last checked
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 の評判はこのドメインに起因しません。
harvey.ns.cloudflare.comruth.ns.cloudflare.comLocation describes the IP network.
fa717f510a3f9e5c700ee6fe21a13722893c60cef5b7cd660714b6bf8103fc29Saved 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 speccy.software · checked Jul 6, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
speccy.software
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
redirected→live_content
content_served
不明→redirected
http_redirect
不明→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
6 community references
View source9/89 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcespeccy.software
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 ↗
speccy.software)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.