VirusTotal
21 / 89
2025-beta.vercel.app was observed returning an HTTP 451 status on 2026-10-03, indicating restricted access at that time. Google Safe Browsing flagged the domain for social engineering on 2026-09-13, providing a security-related observation.
The domain returned HTTP status 451 on 2026-10-03. Google Safe Browsing identified social engineering threats on 2026-09-13. VirusTotal recorded 21 detections out of 89 scanners on 2026-09-13. The domain was included in the PhishDestroy internal listing as of the blocklist check on 2026-10-04.
These records from Google Safe Browsing, VirusTotal, and the PhishDestroy internal listing offer several distinct security-related perspectives on 2025-beta.vercel.app. The HTTP 451 response documents restricted access on a specific date, while security sources provide their findings independently.
For 2025-beta.vercel.app, retain the HTTP status and all security source records for ongoing reference. Compare the Google Safe Browsing, VirusTotal, and PhishDestroy internal listing results with future updates. Base any further review of the domain on these recorded findings.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
VercelScanner note: dead_http: raw=http_451; http=451; via=https_proxy; server=Vercel; provider_error=DEPLOYMENT_DISABLED
Provider response during scan: DEPLOYMENT_DISABLED
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
12 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