https://uber.com
69.48.216.87 · Uber Technologies, Inc
San Francisco, United States
11231 days
200 · 36.0s
Valid· DigiCert Global G2 TLS RSA SHA256 2020 CA1, DigiCert Inc, US
COMPLETED
No KB/IOK detections were recorded for this scan.
technology | transportation | mobility | other · 4/15/2026
The page presents Uber branding on the official domain uber.com with Uber visuals and content. There is no clear credential harvesting or login form observed in the static HTML; however, the page loads a large set of third-party scripts and tracks user interactions via numerous POST endpoints to Uber APIs, which is expected for a first-party Uber interface. The evidence does not clearly indicate impersonation or phishing; the branding appears consistent with Uber's own site on its official domain, though the extensive external script usage and POST activity warrant normal security monitoring for data handling and privacy implications.
Capture
Stages: 3
Canonical: Late Render (+3s)
Changed: No
Credential Signals
Forms: 1
Password fields: 0
Late-stage login UI: No
Resource Signals
Resources: 215
Hosts: 7
Domains: 3
Suspicious Endpoints
hxxps://www[.]uber[.]com/api/getCurrentUser?localeCode=en
hxxps://www[.]uber[.]com/api/getProductSuggestions?localeCode=en
hxxps://www[.]uber[.]com/api/getMapHeroEnabledProducts?localeCode=en
hxxps://www[.]uber[.]com/api/getMerchandisingAdAvailability?localeCode=en
hxxps://www[.]uber[.]com/api/pudoLocationSearch?localeCode=en
hxxps://www[.]uber[.]com/api/getExperiments?localeCode=en
No suspicious indicators identified
The scan indicates the site on its official domain Uber.com with legitimate Uber branding and typical analytics/telemetry endpoints. There is no evidence of credential harvesting UI or impersonation in the static content. However, the heavy use of external tracking scripts and frequent POST calls to account-related endpoints could raise privacy/telemetry concerns if data is mishandled. No action is warranted for phishing at this time; continue monitoring for unusual data exfiltration patterns or unexpected endpoint usage. If there is any doubt about the page rendering a credential form, it would require runtime analysis beyond static HTML to confirm.
Monitor