The domain cryptohelpdesk.online was registered on February 21, 2026 through HOSTINGER operations, UAB and is currently taken offline. VirusTotal records show that four of ninety‑three security vendors flagged the domain, indicating a modest level of detection across the scanning community. The site resolves to IP address 82.25.102.218, which belongs to AS47583 Hostinger International Limited and is geolocated in Germany. Both authoritative name servers are ns1.dns-parking.com and ns2.dns-parking.com, typical of parked or parking‑service domains.
Gridinsoft assigns a trust score of zero out of one hundred, reinforcing the malicious assessment. The page title returned by the server is "CryptoHelpDesk", and the site is classified as a Tech Support Scam that deploys a Solana Drainer kit to exfiltrate cryptocurrency assets. No SSL certificate is presented, meaning traffic is unencrypted and can be intercepted or tampered with. The domain appears on four security blocklists and is explicitly blocked by PhishDestroy, Polkadot, Enkrypt, and Codeesura, demonstrating that multiple defensive feeds already recognize it as hostile.
Although the site is presently offline, defenders should continue to enforce blocks at the DNS and proxy layers, monitor for any resurrection attempts, and consider sinkholing the associated IP range. Network sensors should alert on outbound connections to 82.25.102.218 and any DNS queries for cryptohelpdesk.online. Given the low trust score, the presence on multiple blocklists, and the confirmed use of a Solana drainer kit, the domain should be treated as high‑risk and fully denied in corporate environments.
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-19 01:08:16 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-16 22:11:06 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 22:11:06 UTC → 2026-09-30 16:14:55 UTC · 2,538.06hmidpoint estimate ≈ 2026-08-08 19:13:00 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.
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='cryptohelpdesk.online', port=80): Max retries exceeded with url: / (Caused by NewConnectio
cryptohelpdesk.online
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
PDF notice generated Notice text archived (1,277 chars)
Abuse notice text as sent to the provider
Policy Violations:
Section 3.1 of the AUP: The domain cryptohelpdesk.online is engaged in phishing activities, which constitutes a clear violation of your Acceptable Use Policy prohibiting illegal activities and deception.
Section 4.2 of the TOS: The domain's operation involves fraudulent practices aimed at misleading users, thereby violating the terms that reserve your right to suspend or terminate services for such violations.
Applicable Laws (Unknown):
Computer Fraud and Abuse Act (CFAA): This U.S. federal law prohibits unauthorized access to computers and networks, including phishing schemes that deceive users into providing sensitive information.
Wire Fraud Statute (18 U.S.C. § 1343): This law criminalizes schemes to defraud individuals or entities through electronic communications, which applies to the fraudulent activities conducted via cryptohelpdesk.online.
CAN-SPAM Act (15 U.S.C. § 7701): This act regulates commercial email and prohibits deceptive practices, which are evident in the phishing attempts associated with this domain.
Regulatory Note: Failure to take immediate action against cryptohelpdesk.online may result in liability for facilitating illegal activities and could expose your organization to regulatory scrutiny and potential penalties.
あなたの仮想通貨取引所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
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.
(LT)
