VirusTotal
9 / 91
“Report-USDT Bot”
This domain, walletcheck.digital, is flagged as an active cryptocurrency phishing site targeting users with a crypto drainer scheme. Registered on February 21, 2026, through PDR Ltd. d/b/a PublicDomainRegistry.com, the domain remains operational as of July 12, 2026, with a confirmed HTTP 200 status. Analysis of its infrastructure reveals it resolves to the IP address 135.125.128.255, hosted on AS16276 (OVH SAS) in Germany. The domain employs nameservers dns1.regway.com, dns2.regway.com, dns3.regway.com, and dns4.regway.com, a configuration commonly observed in phishing operations due to its resilience and redundancy. The page title, Report-USDT Bot, suggests the site is designed to deceive users into interacting with a fraudulent USDT (Tether) bot, likely intended to drain cryptocurrency from connected wallets. Security vendors have begun flagging the domain, with 2 out of 95 engines on VirusTotal identifying it as malicious, and it appears on four independent security blocklists. The domain’s SSL certificate, issued by Let’s Encrypt, provides encryption but does not validate the legitimacy of the site, a tactic frequently exploited by threat actors to lend a false sense of security to visitors. While the exact mechanics of the drainer remain unconfirmed due to the absence of direct analysis of the site’s content, the combination of its registration details, hosting infrastructure, and security flags strongly indicates malicious intent. Defenders should treat this domain as high-risk and prioritize blocking it at the DNS or network level. Organizations should also monitor for connections to 135.125.128.255 and the associated nameservers, as these may serve additional phishing or malware distribution campaigns. Given the domain’s recent creation and active status, further monitoring is recommended to track any shifts in its infrastructure or targeting patterns.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: terminal_unconfirmed: candidate_reason=hosting_placeholder; raw=placeholder; http=200; via=https_direct; server=nginx
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.
dns4.regway.comLocation describes the IP network.
ee1812b4a4b6a39c1285b7f33dbddf9b6dc35b75022104f9a943994d9fd79c74license.luanatic.devSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 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.
Reported by 1 community member, first seen Sep 16, 2025
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