boiwithyew.vercel.app returned an HTTP status 404 on 2026-10-01, as recorded during the most recent HTTP check. The domain is also listed in the PhishDestroy internal catalogue, which is maintained by the publisher.
Recorded Evidence
The HTTP check on 2026-10-01 recorded a 404 response for boiwithyew.vercel.app. VirusTotal reported 16 detections out of 89 scanners on 2026-09-17. The domain appears in the PhishDestroy internal listing. PageSpeed recorded a performance score of 100 on 2026-09-15. The domain was first observed on 2026-09-06.
Interpretation
Each source provides a distinct observation about boiwithyew.vercel.app. The HTTP status 404 reflects only the response on the date of the check. VirusTotal’s detection count and scanner total are limited to a single scan, while the PhishDestroy entry indicates the domain’s inclusion in a publisher-managed catalogue. The PageSpeed score and first observation date supply additional context but do not indicate current content or use.
Recommended Actions
Review the HTTP check and VirusTotal scan results for boiwithyew.vercel.app as separate records. Retain the PhishDestroy listing for reference and compare it with the VirusTotal report for consistency. Conduct a new HTTP check for boiwithyew.vercel.app and keep the result with previous findings.
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-13 22:06:02 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:06:02 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: 16 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
Netcraft
Sophos
URLQuery
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of boiwithyew.vercel.app· checked Sep 15, 2026
100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
0.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.8s
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.
Domain Status Transition2026-10-09 01:25:38 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-15 10:00:19 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 07:13:13 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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.
(US)
