The domain rewards-solayer.foundation is a confirmed brand impersonation phishing site targeting users of the Solayer platform. It poses as a legitimate Solayer airdrop page, as indicated by its page title 'Solayer | Hardware-accelerated SVM', and is classified as an airdrop scam. The site has been taken offline, but it posed an elevated risk due to its ability to deceive users into connecting wallets or sharing credentials.
Technical analysis shows that rewards-solayer.foundation was flagged by 1 of 95 VirusTotal vendors, including Gridinsoft, and appears on 2 security blocklists (PhishDestroy, ScamSniffer). The domain was registered on September 19, 2025, through PDR Ltd. d/b/a PublicDomainRegistry.com, and resolves to IP address 104.21.2.170, hosted in the US by Cloudflare, Inc. (AS13335). No SSL certificate was issued, and the Gridinsoft trust score is 0/100. Google Safe Browsing did not flag this domain.
Users who interacted with rewards-solayer.foundation should take immediate safety steps. Since this is an airdrop scam, victims should revoke any token approvals granted to the site using a blockchain explorer or a revoke tool, and move all funds to a new wallet with a fresh seed phrase. If credentials were entered, change passwords for associated accounts and enable two-factor authentication. Report the domain to PhishDestroy and ScamSniffer, and file a complaint with the Federal Trade Commission or relevant cybersecurity authorities.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='rewards-solayer.foundation', port=80): Max retries exceeded with url: / (Caused by NewConn
DOM Analysisanalyzed 2026年4月23日score 20/1005 brand signals
Submitted URLhttps://rewards-solayer.foundation/
ICANN OVERSIGHT
认证和 RAA 背景
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 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:11:11 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-17 22:12:48 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:12:48 UTC → 2026-09-30 16:14:55 UTC · 2,514.04hmidpoint estimate ≈ 2026-08-09 07:13:51 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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(IN)
