Hostname
julo-store.com
Last fetched
julo-store.com resolves to 13.227.192.20, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. julo-store.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
- 13.227.192.20
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.23
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.49
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.99
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.227.29
13.227.227.0/24 · AMAZON-02 - Amazon.com, Inc. · Hanoi, VN
- 13.227.227.31
13.227.227.0/24 · AMAZON-02 - Amazon.com, Inc. · Hanoi, VN
- 13.227.227.4
13.227.227.0/24 · AMAZON-02 - Amazon.com, Inc. · Hanoi, VN
- 13.227.227.98
13.227.227.0/24 · AMAZON-02 - Amazon.com, Inc. · Hanoi, VN
- 18.239.134.21
18.239.134.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 18.239.134.32
18.239.134.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 18.239.134.47
18.239.134.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 18.239.134.49
18.239.134.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 99.84.152.121
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.68
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.7
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.79
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for julo-store.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:120
Mail and authentication
Nameservers
- ns-15.awsdns-01.com
- ns-679.awsdns-20.net
- ns-1368.awsdns-43.org
- ns-2017.awsdns-60.co.uk
Threat-feed evidence
History
Related pages
Pivot from julo-store.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: "julo-store.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.