Hostname
themedicube.tw
Last fetched
themedicube.tw resolves to 121.254.178.231, announced in 121.254.128.0/17 by LGDACOM-KR - LG DACOM Corporation in KR. themedicube.tw 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
- 121.254.178.231
- 13.227.192.116
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.45
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.52
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.62
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 52.222.136.129
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.52
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.71
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.85
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for themedicube.tw is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for themedicube.tw. 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.
Subdomains
| Subdomain |
|---|
| www.themedicube.tw |
Showing 1 of 1 subdomain (1 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-301.awsdns-37.com
- ns.gabia.co.kr
- ns1.gabia.co.kr
- ns-657.awsdns-18.net
- ns.gabia.net
- ns-1123.awsdns-12.org
- ns-2036.awsdns-62.co.uk
Threat-feed evidence
History
Related pages
Pivot from themedicube.tw 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: "themedicube.tw"})-[: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.