VirusTotal
8 / 89
“Create Next App”
On 2026-10-01, business-metta-integrity.vercel.app returned HTTP status 451 according to the recorded HTTP check. The domain was first observed on 2026-09-17.
The HTTP check on 2026-10-01 recorded status 451 for business-metta-integrity.vercel.app. VirusTotal recorded 8 detections out of 89 scanners on 2026-09-21. The PhishDestroy internal listing is recorded as true on 2026-09-17.
These records represent separate dated observations rather than a single verified state. The HTTP status, VirusTotal ratio and PhishDestroy listing each come from their own dated source, so they should be compared as distinct data points. The chronology from first observation to the HTTP check spans recorded dates, but those dates alone do not establish a change in behavior.
For business-metta-integrity.vercel.app, preserve the HTTP check record and the PhishDestroy internal listing as separate source records. Compare the VirusTotal detection record against the HTTP check record without merging their metrics. Retain the first-observed record for later comparison.
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_direct; 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.
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
16 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