Hostname
izaking.cc
Last fetched
izaking.cc resolves to 122.116.117.181, announced in 122.116.0.0/16 by HINET - Data Communication Business Group in TW. izaking.cc 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
IPv6 resolution
No AAAA record for izaking.cc is recorded in WhisperGraph.
Attribution
chunghwa
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1327
- Registrant organisation
- registration privacy, no-ip.com
- Contact emails
- 039b56a3361c6b63-573014@privacy.no-ip.com, 0a3f28a4a6c094b3-573014@privacy.no-ip.com, 2cd521117abda2d1-573014@privacy.no-ip.com, 329ccbf1bc76d48c-573014@privacy.no-ip.com, 3d535879b2e9df1f-573014@privacy.no-ip.com, 407531cd15d9c9aa-573014@privacy.no-ip.com, 414d1d8255c2784e-573014@privacy.no-ip.com, 4b2e0a9dd5feada8-573014@privacy.no-ip.com, 50aea112238b707a-573014@privacy.no-ip.com, 815077788616f878-573014@privacy.no-ip.com, 89a0a1c9533631d9-573014@privacy.no-ip.com, 9fffd9f710b2a0e5-573014@privacy.no-ip.com, ac50e29d4d6142b9-573014@privacy.no-ip.com, b67503147c6bcf04-573014@privacy.no-ip.com, c13505bc4769d1a4-573014@privacy.no-ip.com, c40f0745da943c65-573014@privacy.no-ip.com, c605addbc16c45a1-573014@privacy.no-ip.com, dc6c8d8a53bff190-573014@privacy.no-ip.com, e2a473bf63f7b72a-573014@privacy.no-ip.com, eba449522098db12-573014@privacy.no-ip.com
Subdomains
Mail and authentication
Nameservers
- ns1.no-ip.com
- ns2.no-ip.com
- ns3.no-ip.com
- ns4.no-ip.com
- ns5.no-ip.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mail.izaking.cc
Threat-feed evidence
History
Related pages
Pivot from izaking.cc 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: "izaking.cc"})-[: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.