Skip to content
https://uber.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 904 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 904 B Sitemaps referenced 1 User-agents *, AdsBot-Google, Googlebot-Image Blocking No — crawling allowed
# robotstxt.org/
User-agent: *
allow: *.js
allow: *.css
disallow: /invite
disallow: /report-issue
disallow: */?_ga
disallow: *?gh_jid
disallow: */?client_id
disallow: */?realestate_id
disallow: */go/
disallow: */cmlntest-access
disallow: */api/
disallow: */custom-api/
disallow: */_uwa
disallow: /app/
disallow: /local/search
disallow: /local/*?*sort
disallow: /local/*/*/*/*/
disallow: /in/hi/e/*
disallow: /in/bn/e/*
disallow: /in/kn/e/*
disallow: /in/mr/e/*
disallow: /in/ta/e/*
disallow: /in/te/e/*
disallow: /in/ur/e/*
disallow: /*?id=
disallow: /*&id=
disallow: /*?*userId=
disallow: /*?*uber_client_name=
disallow: /*?*requestToken=
allow: /.well-known/

User-agent: AdsBot-Google
Disallow: */_uwa

User-agent: Googlebot-Image
Disallow:


sitemap: https://www.uber.com/sitemap.xml


disallow: /ch/en/

disallow: /in/ur/

disallow: /jp/zh/

disallow: /kr/zh/

disallow: /ma/fr/

disallow: /ma/en/
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
306 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

306
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 16 ms lookup
PASS
1 A records, 16 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 69.48.216.5
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: edns126.ultradns.biz, edns126.ultradns.com, edns126.ultradns.net, edns126.ultradns.org
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 16 ms
Got: 16 ms
A69.48.216.5
AAAA
CNAME
NSedns126.ultradns.biz, edns126.ultradns.com, edns126.ultradns.net, edns126.ultradns.org
MX
2 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
AD5-G1R-7NJ
_pgze0p8hg7pyp30yid9q2dokz00180z
crz6wwryflvvfk4kvk5lqfk78p02dc7m
ca3-ffffa27c6ab6493ba5e2ffd4f8961467
f621e431-a485-4094-8587-2f76f441ccab
mandrill_verify.5Qnmy5yihDZ4mJwXJ0VP7w
mandrill_verify.UYz1FLL51N9Ky3RCgCUZGQ
apple-domain-verification=NGLGgklojeSRTo9T
MS=607A6B094E5395250B2F88D76D42FFB6DC2C18A4
c9s6q2+D+iTzxyax7z2ol/gbj0Rqq8Loojleaq22ZDM=
SFMC-4eGhjXSll4RESL8vyX0CBVbTfffzejZShsyAXBrT
docusign=635f0402-4f58-42de-8e07-e1da6d8a971a
docusign=ce93a9f0-d430-4abb-aee8-ec66524c1f12
autodesk-domain-verification=wa1khlrPnOY-93pE5_nH
openai-domain-verification=dv-wtb3VIyo0DtnGsiQN4DnZ4c7
docker-verification=e121526a-c4bd-4829-8f6b-c4a3c93f0029
lovable_verification=workspace_01jz0y1v0ff9cv8hsxkbvawqhx
facebook-domain-verification=fgnbsxqefhg2pzugzl4vcw82ylgagg
mixpanel-domain-verify=a35ee3f7-3848-4a0b-822e-d429b507c0c6
uber-site-verification=56157b0f-0f5f-4bdc-8a64-9c313ac173a5
workplace-domain-verification=HhUs1CkDiWsL4Nlmkdb6IOVjrebKb1
beautifulai-site-verification=ed0fad99-1b20-4963-ab5b-538f0f915117
google-site-verification=9kwu-dlf_JSf0XtaHK2xK-Cowpra8TnHbfTRCa7NBk0
google-site-verification=bywbMPdGdGaSev-nAuHwbdYjZziw9oPeGkOgBD5UyK0
google-site-verification=p21addAHCLTiBqVhN6P3leSJNO2ob8edJtQbICdXCj8
google-site-verification=yHvJ7x6qUkjrzRfaPzSO5Iu42eP70uSS0Q88xPFBbSU
apple-domain-verification=Da2R4Md5eAUVUg038WJnE-_ifFtCwYYc_Dlmx3EaPsU
notion-domain-verification=ReKaEX54F5cGF2V3IKgyilPZF3TjQ34Iua63ng0LHDC
atlassian-sending-domain-verification=0302bdf3-f835-4464-979d-7beeda0dbe97
stripe-verification=79f7b9921824c7fd1cd4ffc20fc10f662a5322317c8290f124b4e18d9ebd...
duo_sso_verification=efpKKW3WtEX7Ln6CBDAQyyNA5mwOU0KxFopDN2LtcawWUcGa6BByYIq5LG6...
duo_sso_verification=EArnP8qJQk9QUv3i30tGmhVOfsuivQxEgBlNLIF8EaD3ZimeyV2Iq5rBJQH...
Dynatrace-site-verification=95915cac-be11-4e1a-81b7-9580122d59d1__vrv8sf7b41uebr...
atlassian-domain-verification=M5S2mTVz1nn58QsIgP0q4BLRplQvKva5IHHG5usoAYecrD00FT...
atlassian-domain-verification=MMotF76tU47LiNcsEf06+lzKmWly4PgbYpYZqHy3a9YdTdY4S4...
hpe-greenlake-domain-verification=6553304837784b7232736d71514737737353622d685435...
paloaltonetworks-site-verification=f567a8ba5a35da704fb1e540c1e50bbaa33bc2ea6b871...
SPF v=spf1 include:uber.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.v...
postman-domain-verification=4c640467e16a94ba218b31f435eb42e0749d16ab4168939f9ad5...
CAALookup not available with standard resolver
Resolved in 16 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 105 ms total
PASS
1 redirect(s), 105 ms total
Info::
Single redirect
Got: https://uber.com → https://www.uber.com/ (301)
Info::
WWW normalization redirect

https://uber.com

41 ms · HTTP/1.1

301

https://www.uber.com/

64 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uber.com30141 msHTTP/1.1ufe
2https://www.uber.com/40664 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

406https://www.uber.com/
200https://uber.com/

HTTP → HTTPS

301http://uber.com/ https://uber.com:443/

Consistent

A+
Domain Intelligence
uber.com — via MarkMonitor Inc., 31 years, 2 months old, hosted on Google Cloud
PASS
uber.com — via MarkMonitor Inc., 31 years, 2 months old, hosted on Google Cloud
Info::
Domain registered until Jul 13, 2028 (2 years, 3 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

730 days

July 13, 2028

SSL certificate

306 days

Issued by DigiCert Inc

Domain age

31 years, 2 months

Registered July 14, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

69.48.216.5

Registrar

MarkMonitor Inc.

Unlocked 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created July 14, 1995 (31 years, 2 months ago)
Expires July 13, 2028 (2 years, 3 months)
Last Updated December 15, 2021
Name Servers dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, edns126.ultradns.biz, edns126.ultradns.com, edns126.ultradns.net, edns126.ultradns.org
DNSSEC Not enabled
Hosting
IP Address 69.48.216.5
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 81 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
81 ms
Total Time Total request time from DNS lookup through full response.
82 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 7 ms TLS Handshake 10 ms Server Processing 61 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback