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.
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-19 01:09:55 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
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3838.83
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='solidity.center', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
solidity.center
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
