On 2026-10-01, consendomitobt.vercel.app returned an HTTP 404 status code in the recorded HTTP check. The same source set shows a first observation date of 2026-08-26 for the domain, and the IP address 64.29.17.195 is recorded with the organization Vercel, Inc in the United States.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 404 for consendomitobt.vercel.app. VirusTotal, checked on 2026-09-04, recorded 14 detections across 90 scanners. PhishDestroy's internal listing records the domain, and the first observation is dated 2026-08-26.
Interpretation
The HTTP 404 record describes only the response captured on its check date, not all content that may exist on the domain. The VirusTotal figures describe scanner output on a separate date, so the two records should be read as distinct observations rather than a combined measure. The PhishDestroy listing and the first observation date give a chronology for when the domain entered monitoring records.
Recommended Actions
Preserve the HTTP check record for consendomitobt.vercel.app and the VirusTotal entry as separate source documents. Compare the PhishDestroy listing against the first observation record to see how the domain's recorded footprint develops. Re-check the domain's HTTP response and scanner results at a later point and keep each new record alongside the existing ones.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:05:31 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:05:31 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: 14 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
MalwareURL
Netcraft
Sophos
Webroot
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:23:06 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-02 22:00:23 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-02 19:33:10 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)
