VirusTotal
13 / 93
“RustHollow | Community for RUST Skin Designers”
As of July 23, 2026, the domain rusthollow.design is flagged for brand impersonation, specifically targeting the Steam community. The domain was registered through Web Commerce Communications Limited on November 10, 2025, and has since been taken offline. Infrastructure analysis reveals that the domain was hosted in Russia under the AS57724 DDOS-GUARD LTD network, resolving to the IP address 185.178.208.158. The domain is associated with nameservers ns1.ddos-guard.net and ns2.ddos-guard.net, which are known for providing DDoS protection services but can also be used by malicious actors to evade detection.
Gridinsoft has assigned this domain a trust score of 0/100, indicating a high level of suspicion. The domain appears on one security blocklist, PhishDestroy, and has been flagged by 13 out of 93 security vendors, further corroborating its malicious nature. Analysis indicates that the page title for the domain was 'RustHollow | Community for RUST Skin Designers,' which could be used to mislead visitors into believing it is an official or affiliated community for the game RUST.
The lack of an SSL certificate adds to the domain's suspicious profile, as legitimate sites typically use SSL to secure connections. Despite the domain being currently offline, defenders should remain vigilant and block access to prevent any potential residual threats. The exact content and functionality of the site have not been analyzed, but the available evidence strongly suggests that it was used for brand impersonation, posing a risk to Steam users and the broader gaming community.
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='rusthollow.design', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
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.ddos-guard.netns2.ddos-guard.netLocation describes the IP network.
12 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 Nov 10, 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