Analysis of secure-wallet.online indicates this domain was actively involved in a wallet/seed phishing operation targeting cryptocurrency users. The domain was registered on February 21, 2026, through Web Commerce Communications Limited (WebNic.cc) and resolved to 185.208.156.66, an IP address hosted in Switzerland under AS42624 (Global-Data System IT Corporation). The SSL certificate was issued by R11, a low-assurance certificate authority often associated with fraudulent sites. The page title, 'Professional Crypto Wallet Recovery Service,' explicitly suggests the domain was designed to deceive victims into disclosing wallet recovery phrases or private keys.
Security vendors flagged the domain with a Gridinsoft trust score of 0/100, and it was blocked by PhishDestroy. Five of 93 security vendors on VirusTotal detected the domain as malicious. The domain appears on one security blocklist and was referenced in an AlienVault OTX threat intelligence pulse, confirming its classification as part of a recovery scam phishing kit. The brand target is identified as 'across,' though no further details on the specific impersonation tactics are available.
As of July 24, 2026, the domain is offline, but defenders should treat any past or future resolution of this domain as high-risk. Organizations are advised to block the domain and its associated IP (185.208.156.66) at the network level, monitor for credential submissions tied to this infrastructure, and alert users who may have interacted with the site. No evidence suggests the domain was used for other scam types beyond wallet/seed phishing.
DOM Analysisanalyzed 2026년 3월 24일score 88/10011 brand signals
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:00:58 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:00:58 UTC
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.
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(CA)
