On 2026-10-01, livedesktop.plasmic.run returned an HTTP 308 status code, documenting a redirect response at that time. The domain was also observed in the PhishDestroy internal catalogue, indicating it was flagged for review by that publisher.
Recorded Evidence
The HTTP check on 2026-10-01 recorded a status code of 308 for livedesktop.plasmic.run. The PhishDestroy internal listing was marked on 2026-09-12. VirusTotal scanned the domain on 2026-09-20, reporting 17 detections out of 89 scanners. The PageSpeed check on 2026-09-12 returned a performance score of 49. The SSL certificate was issued by Let's Encrypt / YR1 and scanned on 2026-09-12.
Interpretation
These source observations provide distinct records from multiple dates, allowing comparison of technical responses and catalogue listings. The HTTP 308 status documents only the response captured at the time of the check and does not describe all domain content. The VirusTotal detections and PhishDestroy internal listing are separate records that can be used for further review.
Recommended Actions
Review the HTTP status, VirusTotal scan, and PhishDestroy internal listing for livedesktop.plasmic.run as separate source records. Preserve the PageSpeed performance score and SSL certificate scan for future comparison. Use these documented observations to inform any ongoing monitoring or additional checks.
DOM Analysisanalyzed 2026年9月12日score 88/1004 brand signals
Submitted URLhttps://livedesktop.plasmic.run/
Favicon Hash
ICANN OVERSIGHTRegistration: plasmic.run
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For the registrable domain plasmic.run behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
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.
Certificate fingerprintec8e362847a5ecbb00ffaebc10be1eb8492cbf61cc41bffeec027bb8c775c772Certificate names · 1 SANs
plasmic.run
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:25:34 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:25:34 UTC
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.
技术 · 1 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed First positive detection Previous stored snapshot: 10 detections
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
卡巴斯基
LevelBlue
Lionic
Netcraft
SOCRadar
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of livedesktop.plasmic.run· checked Sep 12, 2026
49
Poor
Performance
FCP
2.89s
First Contentful Paint
LCP
5.97s
Largest Contentful Paint
CLS
0.509
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.75s
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.
Threat First Observed2026-09-12 10:28:03 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.150.1.1.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
