Security engines reporting a detection: 7. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='solaeyer.foundation', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Feb 7, 2025 —Expires Feb 7, 2026
Time to First Unavailability232 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 17, 2025
DOM Analysisanalyzed Apr 23, 2026score 80/100
Submitted URLhttps://solaeyer.foundation/
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:10:10 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-14 22:22:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-14 22:22:15 UTC → 2026-09-30 16:14:55 UTC · 2,585.88hmidpoint estimate ≈ 2026-08-07 19:18:35 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
solaeyer.foundation detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 8, 2026
Time to First Unavailability
5579 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
5 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · solaeyer.foundation
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(MY)
