VirusTotal
7 / 95 engine detections
Buka laporan“Sorry, the website has been stopped”
Phishing: solaeyer.foundation — Konten tidak tersedia. Ringkasan bukti: VirusTotal 7/95 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
7 / 95 engine detections
Buka laporan1 community reference
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults 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.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
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.
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/57d067b2-cdf5-4a2c-8b96-67ac4fbd9d74
Dapat dijangkau→Tidak tersedia
7/95 engine detections
View sourcePage captured
View sourceNo threat flag
View source1 community references
View sourcesolaeyer.foundation
View sourceDilaporkan oleh 1 anggota komunitas; pertama terlihat 17/09/2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.