Hostname
assets.krrt.io
Last fetched
assets.krrt.io resolves to 13.227.192.125, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. assets.krrt.io 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.125
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.17
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.30
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.9
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.32.99.2
13.32.98.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.99.29
13.32.98.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.99.82
13.32.98.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.99.99
13.32.98.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 143.204.181.18
143.204.176.0/21 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 143.204.181.30
143.204.176.0/21 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 143.204.181.59
143.204.176.0/21 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 143.204.181.119
143.204.176.0/21 · AMAZON-02 - Amazon.com, Inc. · London, GB
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for assets.krrt.io. 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
Nameservers
- ns-163.awsdns-20.com
- ns-668.awsdns-19.net
- ns-1099.awsdns-09.org
- ns-1885.awsdns-43.co.uk
Threat-feed evidence
History
Related pages
Pivot from assets.krrt.io 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: "assets.krrt.io"})-[: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.