Skip to content

Hostname

cuenote.jp

Last fetched

cuenote.jp resolves to 158.201.241.10, announced in 158.201.224.0/19 by HANSHIN - ITEC HANKYU HANSHIN CO.,LTD. in JP. cuenote.jp is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · cuenote.jpRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.2/10canon.whisper.security/host/cuenote.jp

Resolution chain

IPv6 resolution

No AAAA record for cuenote.jp is recorded in WhisperGraph.

Attribution

itec hankyu hanshin

ORIGIN_AS

WHOIS identity

Registrant organisation
ymirlink
Contact emails
domain@ymir.co.jp

Subdomains

Subdomain
0804-010.cuenote.jp
1107-004.cuenote.jp
1205-016.cuenote.jp
1205-017.cuenote.jp
1309-023.cuenote.jp
ae-demo606.cuenote.jp
ae0411.cuenote.jp
ae0421.cuenote.jp
ae6238.cuenote.jp
ae8507.cuenote.jp
airlink.cuenote.jp
anpi.cuenote.jp

Showing 12 of 2,870. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • dns1.asp.cuenote.jp
  • dns1.cuenote.jp
  • dns2.cuenote.jp
  • 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.ymir.co.jp

Threat-feed evidence

History

Related pages

Pivot from cuenote.jp 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: "cuenote.jp"})-[: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 20

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