VirusTotal
7 / 95 engine detections
レポートを開く“Sorry, the website has been stopped”
フィッシング: solaeyer.foundation — コンテンツが利用できません. 証拠の概要: VirusTotal 7/95 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data); 3 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 95 engine detections
レポートを開く1 community reference
レポートを開く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 solaeyer.foundation, created on February 07, 2025 and registered through Web Commerce Communications Limited, shows multiple indicators of malicious activity. The site was hosted on Cloudflare infrastructure (IP 104.21.80.1, AS13335) and used the Cloudflare nameservers clayton.ns.cloudflare.com and gemma.ns.cloudflare.com. No TLS certificate was present, and an HTTP request returned the page title "Sorry, the website has been stopped," confirming that the service has been taken offline. Gridinsoft assigned a trust score of 0 out of 100, and the domain appears on four security blocklists.
Independent blocklist providers PhishDestroy, Polkadot, Enkrypt, and Codeesura have all listed the domain as hostile. VirusTotal scans recorded seven detections out of ninety‑five vendor submissions, reinforcing the suspicion of abuse. AlienVault OTX references the domain in a single threat‑intelligence pulse, and the listed scam type is an NFT scam, indicating that the site was likely used to lure victims into fraudulent non‑fungible token transactions.
While the exact payload or phishing page content is not available, the convergence of a zero trust score, multiple blocklist listings, a non‑zero VirusTotal detection count, and the explicit NFT scam designation provide a strong confidence level that the domain was employed for phishing or fraud. Defenders should continue to block the domain at network and endpoint layers, monitor for any residual DNS queries, and consider adding the domain to internal allow‑list exclusions to prevent accidental access. Ongoing observation of the associated IP range is advised, as Cloudflare hosts many unrelated sites, but the specific host identifier (104.21.80.1) should remain on watchlists pending any re‑activation.
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 の評判はこのドメインに起因しません。
clayton.ns.cloudflare.comgemma.ns.cloudflare.comLocation describes the IP network.
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='solaeyer.foundation', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
solaeyer.foundation
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/57d067b2-cdf5-4a2c-8b96-67ac4fbd9d74
到達可能→利用不可
7/95 engine detections
View sourcePage captured
View sourceNo threat flag
View source1 community references
View sourcesolaeyer.foundation
View sourceコミュニティの 1 人が報告・初回確認 2025年9月17日
Listed 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 ↗
solaeyer.foundation)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.