Hostname
witty.btxkorea.com
Last fetched
witty.btxkorea.com resolves to 17 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in KR.
Nutrition Label
Resolution chain
witty.btxkorea.com resolves to 17 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.209.135.21 | 13.209.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 15.164.141.45 | 15.164.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 15.164.199.24 | 15.164.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 20.194.120.148 | 20.192.0.0/10 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | KR |
| 3.34.211.109 | 3.34.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.34.24.118 | 3.34.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.35.40.19 | 3.34.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.38.36.198 | 3.36.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.38.71.107 | 3.36.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.38.83.27 | 3.36.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.39.176.220 | 3.36.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.39.73.174 | 3.36.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 43.202.39.49 | 43.200.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 52.78.83.169 | 52.78.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 43.202.240.73 | 43.200.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | — |
| 54.116.68.115 | 54.116.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | — |
| 43.200.44.137 | 43.200.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | — |
WHOIS identity
No WHOIS records are currently associated with witty.btxkorea.com in WhisperGraph.
Subdomains
3 observed subdomains of witty.btxkorea.com.
Showing 2 of 3. View all subdomains →
Threat posture
History
Related pages
Pivot deeper into the graph from witty.btxkorea.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "witty.btxkorea.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.