solidity.center poses an active crypto drainer threat, specifically targeting users interested in Solidity development or Ethereum smart contracts. The domain mimics trusted development resources to trick visitors into connecting wallets or downloading malicious payloads that drain cryptocurrency holdings. Analysis shows this is a high-risk site designed to exploit trust in the Solidity ecosystem, with infrastructure built for rapid deployment and evasion of early detection systems. This domain was flagged with critical indicators: VirusTotal shows 2/95 security vendor detections as of the investigation date, indicating it has not yet been widely blacklisted despite active malicious activity. The domain was registered through HOSTINGER operations, UAB on June 04, 2025, and resolves to IP 92.113.23.47, all recent attributes consistent with fly-by-night operations. The use of a Let's Encrypt SSL certificate suggests an attempt to appear legitimate, while the lack of detections highlights the need for proactive user vigilance in the crypto space. Users who visited solidity.center should immediately disconnect any connected wallets and revoke permissions using tools like revoke.cash or wallet-specific permission managers. Scan devices for malware using reputable antivirus software and consider transferring remaining assets to a new wallet with updated security practices. Report the domain to your browser’s safe browsing program and share intelligence with platforms like PhishDestroy to help block this threat across the ecosystem.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='solidity.center', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年7月29日score 56/1001 brand signal
Submitted URLhttps://solidity.center/
案件 ID
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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:22 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-23 17:25:11 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-23 17:25:11 UTC → 2026-09-30 16:14:55 UTC · 3,838.83hmidpoint estimate ≈ 2026-07-12 16:50:03 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.
Google PageSpeed Insights — mobile performance audit of solidity.center· checked Apr 6, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
0.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.99s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
11 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.
