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.
スキャナーに関する注記: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
DOM Analysisanalyzed 2026年7月29日score 56/1004 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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:10:45 UTC
RDAP registration不明
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
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.
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.
(RU)
