Hostname
ubuy.mt
Last fetched
ubuy.mt resolves to 104.18.14.11, announced in 104.18.44.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. ubuy.mt 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.14.11
104.18.44.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.15.11
104.18.44.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 13.226.69.110
13.226.79.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.226.69.15
13.226.79.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.226.69.52
13.226.79.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.226.69.65
13.226.79.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 18.67.161.115
18.67.180.0/24 · AMAZON-02 - Amazon.com, Inc. · Chennai, IN
- 18.67.161.19
18.67.180.0/24 · AMAZON-02 - Amazon.com, Inc. · Chennai, IN
- 18.67.161.44
18.67.180.0/24 · AMAZON-02 - Amazon.com, Inc. · Chennai, IN
- 18.67.161.70
18.67.180.0/24 · AMAZON-02 - Amazon.com, Inc. · Chennai, IN
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ubuy.mt. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| images-cdn.ubuy.mt |
| www.ubuy.mt |
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-509.awsdns-63.com
- april.ns.cloudflare.com
- yadiel.ns.cloudflare.com
- ns-636.awsdns-15.net
- ns-1182.awsdns-19.org
- ns-1772.awsdns-29.co.uk
SPF policy
- include: amazonses.com
Threat-feed evidence
History
Related pages
Pivot from ubuy.mt 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.mt"})-[: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.