VirusTotal
2 / 89
“CryptoGuard — Comprehensive cryptocurrency wallet audit”
Analysis of the domain cryptoguard.digital indicates it is an active high-risk crypto scam site, registered on February 23, 2026, through Web Commerce Communications Limited. The domain resolves to IP address 87.236.16.177, hosted on AS198610 (Beget LLC) in Russia, with nameservers ns1.beget.pro, ns2.beget.pro, ns1.beget.com, and ns2.beget.com. As of July 25, 2026, the site returns an HTTP 200 status, suggesting operational availability, though it lacks an SSL certificate, increasing vulnerability to interception. The page title, 'CryptoGuard — Comprehensive cryptocurrency wallet audit,' implies a focus on cryptocurrency security services, aligning with the classified scam type of 'Crypto Scam' in available threat intelligence.
Detection data is limited but notable: one of 93 security vendors on VirusTotal flags the domain, and it appears on a single security blocklist, specifically PhishDestroy. Gridinsoft assigns a trust score of 0/100, reinforcing the high-risk classification. The site employs technologies including PHP, Vue.js, Nginx, Unpkg, and jsDelivr, which are common in both legitimate and malicious web applications, offering no definitive indication of intent on their own. Infrastructure analysis reveals no evidence of widespread detection or takedown efforts, though the low vendor flag count may reflect limited visibility rather than benign status.
Defenders should treat this domain as actively malicious, particularly in environments handling cryptocurrency transactions or wallet security. Network-level blocking of the IP 87.236.16.177 and associated nameservers is recommended, alongside monitoring for related domains registered through the same registrar or hosted on Beget LLC infrastructure. The exact content and functionality of the site remain unanalyzed; however, the available evidence supports categorizing cryptoguard.digital as a fraudulent crypto audit service targeting users seeking wallet security.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx-reuseport/1.21.1Scanner note: alive_content: raw=ok; http=200; via=http_proxy; server=nginx-reuseport/1.21.1
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
11 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 Feb 23, 2026
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