On 2026-10-03, amazon-react-clone-ten.vercel.app returned an HTTP 200 status, indicating a successful server response on that date. The observed page title was 'Amazon' and the server identified itself with a Vercel server header.
Recorded Evidence
Google Safe Browsing flagged the domain for social engineering on 2026-10-02. VirusTotal recorded 19 detections out of 91 scanners on 2026-09-29. The domain appeared in the internal PhishDestroy listing, and a Pagespeed performance score of 67 was measured on 2026-09-21.
Interpretation
The collected records from Google Safe Browsing, VirusTotal, and PhishDestroy provide a multi-source perspective on amazon-react-clone-ten.vercel.app. These sources document both technical and security-related observations, with the Google Safe Browsing and VirusTotal entries indicating that the domain has been noted by several security tools. The Pagespeed score and server details offer additional technical context for further evaluation.
Recommended Actions
Next steps for amazon-react-clone-ten.vercel.app should include reviewing the Google Safe Browsing, VirusTotal, and PhishDestroy records for ongoing reference. Preserve these dated observations for future comparison and continued monitoring. The HTTP response and Pagespeed score may be useful for technical analysis in subsequent reviews.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: StaleRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-11 10:12:40 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:12:40 UTClast content: 2026-10-11 01:46:35 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.
技术 · 3 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of amazon-react-clone-ten.vercel.app· checked Sep 21, 2026
67
Needs Work
Performance
FCP
2.74s
First Contentful Paint
LCP
12.48s
Largest Contentful Paint
CLS
0.012
Cumulative Layout Shift
TBT
16ms
Total Blocking Time
SI
5s
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.
Status Check2026-09-21 09:04:01 UTC
Telemetry event observed.
Threat First Observed2026-09-21 08:03:11 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
