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.
Recorded Evidence
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.
Interpretation
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.
Recommended Actions
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.
スキャナーに関する注記: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
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-13 01:15:02 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-08-14 01:14:40 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-14 01:14:40 UTC → 2026-09-30 16:14:55 UTC · 1,143.00hmidpoint estimate ≈ 2026-09-06 20:44:47 UTC · precision very low · basis bounded
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.
Last analyzed First positive detection Previous stored snapshot: 6 detections
ESET
Emsisoft
Fortinet
ネットクラフト
SOCRadar
URLQuery
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of rust.connecting-plus.digital· checked Aug 14, 2026
80
Needs Work
Performance
FCP
2.25s
First Contentful Paint
LCP
4.27s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
45ms
Total Blocking Time
SI
4.55s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-07 10:00:34 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-08-14 07:54:40 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
Threat First Observed2026-08-14 01:14:40 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 45.94.47.102.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
