livecdn.plasmic.run returned an HTTP status code 308 on 2026-10-01, as recorded by the HTTP check. A PageSpeed performance score of 50 was also documented for this domain on 2026-09-12.
Recorded Evidence
The PhishDestroy internal listing included livecdn.plasmic.run, with its first observation on 2026-09-12. VirusTotal reported 17 detections out of 89 scanners on 2026-09-20. The SSL scan from 2026-09-12 identified Let's Encrypt / YR1 as the certificate issuer.
Interpretation
The PhishDestroy listing, VirusTotal results, and SSL scan each provide observations from separate dates, which highlights that the evidence reflects different points in time. Comparing these distinct records helps clarify how the domain's technical and security profile may have changed between 2026-09-12 and 2026-10-01.
Recommended Actions
Retain all collected evidence for livecdn.plasmic.run, including the exact dates and sources, to support future comparisons. When conducting additional checks, record the date and source for each new observation. Avoid submitting sensitive information to livecdn.plasmic.run while the evidence is under review.
DOM Analysisanalyzed 2026年9月12日score 88/1009 brand signals
Submitted URLhttps://livecdn.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:22 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:25:22 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: 11 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 livecdn.plasmic.run· checked Sep 12, 2026
50
Needs Work
Performance
FCP
3.01s
First Contentful Paint
LCP
6.11s
Largest Contentful Paint
CLS
0.549
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.59s
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:05 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.150.16.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.
