The domain www.wallet-detector.digital is a confirmed phishing site engaged in brand impersonation targeting AMLBot, a cryptocurrency compliance service. It presented itself as a wallet reporting tool under the page title 'Report Wallet | AML Check' but was designed to deceive users into disclosing sensitive information or interacting with fraudulent cryptocurrency transactions. No drainer kit was identified, and the site is currently taken offline.
Technical analysis of www.wallet-detector.digital shows limited but notable detection: 2 of 95 VirusTotal security vendors flagged the domain, including alphaMountain.ai and SOCRadar. It appears on 1 security blocklist (PhishDestroy) and was registered through Global Domain Group LLC on February 21, 2026. The domain resolved to IP address 87.120.219.250, hosted in Great Britain under AS215540 GLOBAL CONNECTIVITY SOLUTIONS LLP, and used an SSL certificate issued by Hestia Control Panel / host.domain.tld. Google Safe Browsing did not flag the site, and it was found in 1 AlienVault OTX threat intelligence pulse. The site employed Google Web Server, HSTS, and HTTP/3 technologies, and Gridinsoft assigned it a trust score of 0/100.
Users who interacted with www.wallet-detector.digital should immediately change any credentials entered on the site and enable two-factor authentication on their accounts. For cryptocurrency-related exposure, revoke any token approvals granted to unknown contracts and consider transferring funds to a new wallet. Monitor accounts for unauthorized transactions and report the phishing domain to platforms such as Google Safe Browsing, PhishTank, or the impersonated brand’s security team for further action.
スキャナーに関する注記:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='wallet-detector.digital', port=80): Max retries exceeded with url: / (Caused by ConnectTim
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 observation不明Probe Inconclusive20%2026-10-11 01:12:41 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-03-15 17:08:01 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.
使用技術 · 3 identified
Google Web Server
H
HSTS
セキュリティ
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
H
HTTP/3
Miscellaneous
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
13 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
(US)
