VirusTotal
6 / 89
“Uwalet - قدم طلبك”
The domain uwalletcard.vercel.app returned an HTTP 451 response during a check on 2026-10-01, a recorded status for that date. The same domain was first observed on 2026-09-07, giving an earlier dated reference point.
A VirusTotal check on 2026-09-17 recorded 6 detections across 89 scanners for uwalletcard.vercel.app. The PhishDestroy internal listing included uwalletcard.vercel.app, and the SSL certificate was issued by Google Trust Services / WR1, scanned on 2026-09-16. The HTTP check on 2026-10-01 recorded IP address 64.29.17.3 in the US under Vercel, Inc.
The named records describe separate observations rather than one combined measurement. The HTTP 451 response reflects only the response recorded on its check date, and the VirusTotal figures reflect only that scan. Because the observation dates differ, the records allow a reader to compare what each source captured without establishing a trend.
Preserve the HTTP check record, the VirusTotal scan record, and the PhishDestroy listing for uwalletcard.vercel.app as separate dated documents. Compare those source records against later checks of the same domain to see whether the recorded responses and detection figures change. Retain the first-observed entry alongside them so the earliest dated reference remains available.
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.
11 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.
1 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-07T15:17:50.302Z.
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