Hostname
shop.kush.com
Last fetched
shop.kush.com resolves to 100.51.153.155, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. shop.kush.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
- 100.51.153.155
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 23.22.85.11
23.22.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.232.245.229
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.198.160.210
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.173.70.129
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.200.117.145
52.200.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.4.177.202
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.54.70.208
52.54.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.160.108.124
54.160.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.227.228.194
54.226.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.80.181.183
54.80.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.92.252.138
54.92.128.0/17 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for shop.kush.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for shop.kush.com. 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.
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
MX records
- mxa.mailgun.org
- mxb.mailgun.org
SPF policy
- include: mailgun.org
Threat-feed evidence
History
Related pages
Pivot from shop.kush.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: "shop.kush.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.