Hostname
ktor.io
Last fetched
ktor.io resolves to 13.226.94.23, announced in 13.226.94.0/23 by AMAZON-02 - Amazon.com, Inc. in US. ktor.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.226.94.23
13.226.94.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.226.94.67
13.226.94.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.226.94.88
13.226.94.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.226.94.89
13.226.94.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.227.192.124
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.29
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.73
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
- 3.174.46.36
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.47
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.68
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.96
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for ktor.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- jetbrains s.r.o.
Subdomains
| Subdomain |
|---|
| api.ktor.io |
| start.ktor.io |
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.
Sample inbound links
Mail and authentication
Nameservers
- ns-68.awsdns-08.com
- ns-927.awsdns-51.net
- ns-1027.awsdns-00.org
- ns-1977.awsdns-55.co.uk
MX records
- smtp.google.com
Threat-feed evidence
History
Related pages
Pivot from ktor.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: "ktor.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.