Hostname
uber.com
Last fetched
uber.com resolves to 7 IPv4 addresses operated by QOSL-AS-AP Qovic Online Solutions LLP in US. WHOIS lists iana:292 as the registrar.
Nutrition Label
Resolution chain
uber.com resolves to 7 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.36.194.114 | 104.36.194.0/24 | AS396982 | QOSL-AS-AP Qovic Online Solutions LLP | US |
| 104.36.194.5 | 104.36.194.0/24 | AS396982 | QOSL-AS-AP Qovic Online Solutions LLP | US |
| 104.36.194.7 | 104.36.194.0/24 | AS396982 | QOSL-AS-AP Qovic Online Solutions LLP | US |
| 104.36.194.8 | 104.36.194.0/24 | AS396982 | QOSL-AS-AP Qovic Online Solutions LLP | US |
| 104.36.194.94 | 104.36.194.0/24 | AS396982 | QOSL-AS-AP Qovic Online Solutions LLP | US |
| 69.48.216.100 | 69.48.216.0/24 | AS396982 | QOSL-AS-AP Qovic Online Solutions LLP | US |
| 69.48.216.73 | 69.48.216.0/24 | AS396982 | QOSL-AS-AP Qovic Online Solutions LLP | US |
WHOIS identity
- Registrar
- iana:292
- Organization
- domain administrator
- Contact emails
Subdomains
282 observed subdomains of uber.com.
Showing 25 of 282. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from uber.com in the public web crawl.
36,161 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for uber.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email |
| SPF_INCLUDE | mailgun.org |
| SPF_INCLUDE | uber.com._nspf.vali.email |
Related pages
Pivot deeper into the graph from uber.com.
- IP · 104.36.194.114
- ASN · AS396982QOSL-AS-AP Qovic Online Solutions LLP
- Registrar · iana:292
- Country · US
- Email · dev@uber.com
- TLD · .com
- Browse hostnames · ub…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "uber.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.