VirusTotal
1 / 95 engine detections
レポートを開く“Cryptocurrency trading and invest platform”
偽テクニカルサポート: duplicate-disabled-5359.invalid — コンテンツが利用できません. 証拠の概要: VirusTotal 1/95 (SOCRadar); PhishDestroy score 55/100. レジストラ: NETIM.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
1 / 95 engine detections
レポートを開くno 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 as of July 22 2026 indicates that the domain www.toshfts.com was registered on 10 July 2025 through NETIM. The authoritative nameservers are simon.ns.cloudflare.com and tori.ns.cloudflare.com, pointing to a hosting address of 66.29.141.228, which belongs to AS22612 (Namecheap, Inc.) and is geolocated in the United States. TLS termination uses a Sectigo Limited / Sectigo Public Server Authentication CA DV R36 certificate, confirming the presence of HTTPS. The web server reports PHP running behind LiteSpeed, and the page title returned by the HTTP response is “Cryptocurrency trading and invest platform”, suggesting a financial‑themed lure.
The domain is classified as a tech‑support scam that impersonates Apple, aligning with the known brand target. Security telemetry shows that PhishDestroy has blocked the site and it appears on a single external blocklist. VirusTotal analysis recorded a single positive detection out of 95 scanners, and Gridinsoft assigned a trust score of 0 / 100, indicating a high likelihood of malicious intent. MX records list mx1-hosting.jellyfish.systems with priority 5 and an additional host with priority 10, though the second entry is truncated.
The domain’s current HTTP status is offline, confirming that the malicious infrastructure has been taken down. While the available data confirms the use of a crypto‑investment narrative and a tech‑support scam vector, the exact content of the phishing pages, credential‑capture mechanisms, or any associated command‑and‑control infrastructure remain unknown. Defenders should continue to block the IP address 66.29.141.228, add the domain and its MX hosts to email and web filtering policies, and monitor for future re‑use of the hosting provider or certificate. Ongoing observation of related Namecheap assets and of any newly registered domains that resolve to the same IP range is recommended to pre‑empt potential re‑deployment of the campaign.
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 の評判はこのドメインに起因しません。
simon.ns.cloudflare.comtori.ns.cloudflare.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
39de7669961cc6f21c9e95908205386aeb34f4dccd2c95237e4cc44b7cc08e05toshfts.comSaved 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 duplicate-disabled-5359.invalid · checked Mar 2, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-5359.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
duplicate-disabled-5359.invalid
Page captured
View sourceNo threat flag
View source1/95 engine detections
View sourceduplicate-disabled-5359.invalid
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 ↗
duplicate-disabled-5359.invalid)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.