Hostname
ubercel.com
Last fetched
ubercel.com resolves to 34.216.121.206, announced in 34.208.0.0/12 by AMAZON-02 - Amazon.com, Inc. in US. ubercel.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 34.216.121.206
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.155.29.82
35.155.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.224.245.118
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.253.157.208
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.11.85.2
52.10.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.212.147.223
54.212.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
IPv6 resolution
No AAAA record for ubercel.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of ubercel.com owner
- Contact emails
- 29a9071b-9e0d-43b8-87a4-1e29a7be06b9@identity-protect.org, be8ebb04-a18e-4ad3-b650-7eddec9298b3@identity-protect.org, c79dfd83-9c36-498f-b105-f0a7a099192c@identity-protect.org, d3c696ab-ede9-4950-a4eb-b526601a4e26@identity-protect.org, e6c215dd-ccc4-492e-af9f-425f4634a5e2@identity-protect.org, fc3a52a2-5284-4574-8fdb-4ee1c5d445b6@identity-protect.org
Subdomains
| Subdomain |
|---|
| cdn.ubercel.com |
| soporte.ubercel.com |
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-114.awsdns-14.com
- ns-620.awsdns-13.net
- ns-1312.awsdns-36.org
- ns-2001.awsdns-58.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Threat-feed evidence
History
Related pages
Pivot from ubercel.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "ubercel.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.