VirusTotal
14 / 90
“404: NOT_FOUND”
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.
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.
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.
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
VercelScanner note: redirect: raw=redirect_308; http=308; via=http_proxy; location=https://consendomitobt.vercel.app/; server=Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive