On 2026-10-01, disney-clone-nu-green.vercel.app returned an HTTP status code of 200, according to the recorded HTTP check. The same record set shows a first observation date of 2026-09-10, indicating the domain was already being tracked weeks before that response was captured.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 200 for disney-clone-nu-green.vercel.app. A first observation dated 2026-09-10 appears in the same record set. An SSL scan dated 2026-09-16 named Google Trust Services / WR1 as the issuer. VirusTotal, checked 2026-09-24, reported 4 detections across 89 scanners. A PageSpeed check dated 2026-09-18 recorded a performance score of 96. The PhishDestroy internal listing field is recorded as true, and the blocklist check date is 2026-10-01.
Interpretation
The HTTP check and the first observation carry different dates, so the 200 response reflects a single dated request rather than a continuous record. The SSL scan and PageSpeed check were taken on separate days, so certificate and performance values describe those moments only. The VirusTotal count and the PhishDestroy listing were captured on their own dates, which means they cannot be aligned to one instant. Comparing these named sources shows how far apart the observations fall.
Recommended Actions
Reviewers should retain the dated records for disney-clone-nu-green.vercel.app so later checks can be compared against the same fields. Any follow-up HTTP check should be logged with its own date before conclusions are drawn from the earlier 200 response. During review, avoid submitting passwords, payment details or other sensitive information to disney-clone-nu-green.vercel.app until the recorded observations are independently confirmed.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: StaleRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 22:13:01 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:13:01 UTClast content: 2026-10-13 22:13:01 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.
技术 · 6 identified
N
Node.js
Programming languages
Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside a web browser.
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
PhishFort
VIPRE
网站性能分析
Google PageSpeed Insights — mobile performance audit of disney-clone-nu-green.vercel.app· checked Sep 18, 2026
96
Good
Performance
FCP
0.97s
First Contentful Paint
LCP
2.36s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
44ms
Total Blocking Time
SI
4.11s
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-16 16:43:14 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.198.79.131.
威胁响应 Pipeline
发现
Analysis
Monitoring
6 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
disney-clone-nu-green.vercel.app 已检测到并排入队，待进行全面分析
2026年9月10日
Cloudflare Radar Report
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.
(US)
