VirusTotal
6 / 91
“Rust — Explore, Build and Survive”
rust.connecting-plus.digital was observed returning an HTTP 502 error on 2026-10-01, indicating a failed response during a recorded check. The domain was first noted on 2026-08-14, and a PageSpeed performance score of 80 was documented that same day.
PhishDestroy internally listed rust.connecting-plus.digital as of 2026-10-01. On 2026-08-22, VirusTotal reported 6 detections out of 91 scanners, with observation time not specified. The SSL certificate scan on 2026-08-14 showed Let's Encrypt / YE2 as the issuer.
The evidence from PhishDestroy, VirusTotal, and SSL scans was collected on different dates, which means each record reflects a distinct point in time. This separation in observation dates allows for comparison of changes or persistence of findings, but limits the ability to draw conclusions about the domain's status at any single moment.
Retain all dated evidence for rust.connecting-plus.digital, including HTTP responses and security listings, to enable future comparison. When reviewing subsequent records, use the exact dates to track changes and avoid entering sensitive information during any ongoing review process.
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='rust.connecting-plus.digital', port=80): Max retries exceeded with url: / (Caused by NewCo
Location describes the IP network.
bb806641127f8f90f995c86dbbf25f978720b4d8de9758f0c11b670946854380Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of rust.connecting-plus.digital · checked Aug 14, 2026
45.94.47.102. 13 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