Hostname
ubuy.com.ps
Last fetched
ubuy.com.ps resolves to 104.18.0.140, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ubuy.com.ps 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.0.140
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.1.140
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 13.227.246.39
13.227.246.0/24 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 13.227.246.55
13.227.246.0/24 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 13.227.246.58
13.227.246.0/24 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 13.227.246.74
13.227.246.0/24 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 13.35.202.11
13.35.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.202.112
13.35.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.202.23
13.35.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.202.30
13.35.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- registrar:101domain grs ltd.
- Registrant organisation
- redacted | eu registrar
Subdomains
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-447.awsdns-55.com
- dara.ns.cloudflare.com
- ezra.ns.cloudflare.com
- ns-912.awsdns-50.net
- ns-1341.awsdns-39.org
- ns-1637.awsdns-12.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: amazonses.com
Threat-feed evidence
History
Related pages
Pivot from ubuy.com.ps 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.com.ps"})-[: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.