Skip to content

Hostname

yd.02yc.cc

Last fetched

yd.02yc.cc resolves to 20 IPv4 addresses operated by AS55933 in HK.

Nutrition Label

WHISPER CANON · yd.02yc.ccRouting diversity5.9/10Peering density7.0/10MOAS conflict⚠ 2 conflictsThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint7.6/10canon.whisper.security/host/yd.02yc.cc

Resolution chain

yd.02yc.cc resolves to 20 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
103.242.2.120103.242.2.0/24AS55933—HK
154.12.54.199154.12.54.0/24AS979NETLAB-SDN - NetLab GlobalUS
154.13.4.150154.13.4.0/24AS35251ANTI-DDOS - NetLab GlobalUS
154.219.96.118154.219.96.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.219.96.159154.219.96.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.219.96.161154.219.96.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.219.96.193154.219.96.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.219.96.237154.219.96.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.219.96.68154.219.96.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.219.96.74154.219.96.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.222.31.104154.222.24.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.222.31.114154.222.24.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.222.31.224154.222.24.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.222.31.240154.222.24.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.222.31.76154.222.24.0/21AS401701COGNETCLOUD-2 - cognetcloud INCHK
154.29.148.105154.29.148.0/24AS979NETLAB-SDN - NetLab GlobalUS
154.29.148.27154.29.148.0/24AS979NETLAB-SDN - NetLab GlobalUS
154.40.36.55154.40.36.0/24AS979NETLAB-SDN - NetLab GlobalUS
154.40.36.74154.40.36.0/24AS979NETLAB-SDN - NetLab GlobalUS
154.9.26.113154.9.26.0/24AS979NETLAB-SDN - NetLab GlobalUS

WHOIS identity

No WHOIS records are currently associated with yd.02yc.cc in WhisperGraph.

Threat posture

History

Related pages

Pivot deeper into the graph from yd.02yc.cc.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "yd.02yc.cc"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.