VirusTotal
1 / 93
“AMLBot - AML Crypto Checker USDT, BTC, ETH, 5000+ coins”
The domain wallet-check.online was registered on February 21, 2026 and is currently taken offline. Infrastructure analysis shows the domain resolves to the IPv4 address 5.182.38.26, which belongs to Autonomous System AS209847 operated by WorkTitans B.V. in Hungary. The registration was performed through Beget LLC and the authoritative name servers are ns1.beget.com, ns1.beget.pro, ns2.beget.com and ns2.beget.pro. No TLS certificate was observed for the site, indicating that HTTPS was not enabled.
The page title returned by the server, "AMLBot - AML Crypto Checker USDT, BTC, ETH, 5000+ coins", explicitly references the legitimate AMLBot brand, confirming a brand‑impersonation vector aimed at cryptocurrency users. The campaign is classified as a crypto scam and is listed on a single security blocklist; PhishDestroy has actively blocked the domain. VirusTotal records show that one of ninety‑three scanning engines flagged the domain, providing a minimal but non‑trivial detection signal.
While the site is offline, defenders should continue to monitor the associated IP address and the Beget name server infrastructure for any re‑use. Blocking the IP range AS209847 and adding wallet-check.online to local deny lists are advisable. Additional observation of DNS changes or resurgence of the domain would warrant escalation.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='wallet-check.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
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.
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.
ns1.beget.comLocation describes the IP network.
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive