On 2026-10-01, temu-steam.vercel.app returned an HTTP status of 200 according to the recorded HTTP check. The same domain was listed on the PhishFeed external blocklist as of the 2026-10-01 blocklist check, and PhishDestroy's internal listing was also true.
Recorded Evidence
The domain first appeared in these records on 2026-09-15. VirusTotal recorded 16 detections across 91 scanners on 2026-09-29. On 2026-09-21, the SSL scan identified the issuer as Google Trust Services / WR1, and the PageSpeed performance score was 100. The domain resolved to IP address 216.198.79.131, associated with Vercel, Inc in the US.
Interpretation
The PhishFeed listing and the PhishDestroy internal listing are separate source records that both flag this domain, while the VirusTotal detections come from a different scanning method. Because the blocklist check and HTTP check share the 2026-10-01 date, they may reflect the same day's observations, but the first observation on 2026-09-15 and the VirusTotal check on 2026-09-29 fall on different dates. These records do not establish why the domain was flagged or what it currently serves.
Recommended Actions
Preserve the PhishFeed listing and the PhishDestroy internal listing for temu-steam.vercel.app as separate source records. Compare the VirusTotal detection record with the HTTP response record to understand how each source evaluated the domain. Review the PageSpeed and SSL scan results for additional context. Recheck the domain's HTTP status and blocklist presence periodically to see whether the recorded observations change.
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:11:10 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:11:10 UTClast content: 2026-10-13 22:11:10 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.
技术 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of temu-steam.vercel.app· checked Sep 21, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.66s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.21s
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-21 08:03:10 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.
(US)
