wlp66.vercel.app returned HTTP status 200 in an HTTP check recorded on 2026-10-01, the most recent availability observation in this evidence set. The same domain was first observed on 2026-09-15, giving the record a documented observation window of roughly two weeks.
Recorded Evidence
A PageSpeed check on 2026-09-22 recorded a performance score of 96 for wlp66.vercel.app. VirusTotal, checked on 2026-09-23, reported 13 detections across 89 scanners. The PhishDestroy internal listing was recorded as true, and an SSL scan on 2026-09-21 identified the issuer as Google Trust Services / WR1. The domain resolved to IP address 64.29.17.195, associated with Vercel, Inc in the US.
Interpretation
The VirusTotal counts and the PhishDestroy listing are separate source observations, each with its own recorded date, and they should be read as such rather than merged into a single trend. The HTTP 200 response describes only the response recorded on 2026-10-01, not all content served by the domain. The PageSpeed score reflects the single scan on 2026-09-22. Because the source dates differ, the records do not establish simultaneous measurement or a change over time.
Recommended Actions
For wlp66.vercel.app, preserve the HTTP check record and the VirusTotal result as separate artifacts for later comparison. Review the PhishDestroy listing entry alongside the VirusTotal result, keeping each source's own record intact. Compare future HTTP checks against the recorded response, and repeat the PageSpeed scan to build a comparable series. Retain the SSL scan output with the other source records so each observation remains traceable.
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 10:12:11 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:12:11 UTClast content: 2026-10-13 10:12:11 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.
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
カスペルスキー
LevelBlue
Lionic
ソフォス
VIPRE
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of wlp66.vercel.app· checked Sep 22, 2026
96
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
2.13s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
182ms
Total Blocking Time
SI
2.02s
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 07:53:11 UTC
Domain ingestion complete. Initial state is marked as alive.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
脅威の検知
wlp66.vercel.app 検出され、詳細な分析のためにキューに入れられた
2026年9月15日
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.
