Hostname
ubuy.cl
Last fetched
ubuy.cl resolves to 104.18.24.56, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ubuy.cl 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
- 104.18.24.56
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.25.56
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.238.55.109
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.45
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.58
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.59
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.160.150.100
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.160.150.51
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.160.150.90
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.160.150.98
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- registrar:key-systems gmbh
- Registrant organisation
- ubuy co for managing and designing websites w.l.l
Subdomains
| Subdomain |
|---|
| images-cdn.ubuy.cl |
| www.ubuy.cl |
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-439.awsdns-54.com
- april.ns.cloudflare.com
- yadiel.ns.cloudflare.com
- ns-754.awsdns-30.net
- ns-1504.awsdns-60.org
- ns-1602.awsdns-08.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
Threat-feed evidence
History
Related pages
Pivot from ubuy.cl 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: "ubuy.cl"})-[: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.