Skip to content

Hostname

kanaloco.jp

Last fetched

kanaloco.jp resolves to 192.124.249.168, announced in 192.124.249.0/24 by SUCURI-SEC - Sucuri in US. kanaloco.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 · kanaloco.jpRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint4.6/10canon.whisper.security/host/kanaloco.jp

Resolution chain

IPv6 resolution

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

Attribution

sucuri

ORIGIN_AS

WHOIS identity

Registrant organisation
kddi web communications inc.(cpi)
Contact emails
nic@cpi.ad.jp

Subdomains

Subdomain
auth.kanaloco.jp
cts.kanaloco.jp
feed.kanaloco.jp
imakana.kanaloco.jp
k-viewer.kanaloco.jp
media.kanaloco.jp
mypage.kanaloco.jp
nie.kanaloco.jp
prestage.kanaloco.jp
railroad.kanaloco.jp
rinten.kanaloco.jp
stage-auth.kanaloco.jp

Showing 12 of 19. 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

Mail and authentication

Nameservers

  • ns-cloud-b1.googledomains.com
  • ns-cloud-b2.googledomains.com
  • ns-cloud-b3.googledomains.com
  • ns-cloud-b4.googledomains.com

MX records

  • vlmx20.secure.ne.jp
  • vlmx21.secure.ne.jp
  • vlmx22.secure.ne.jp

SPF policy

  • ip: 194.91.0.0/16
  • include: amazonses.com
  • a: kanaloco.jp
  • mx: kanaloco.jp
  • include: spf.repica.jp
  • include: 244017673.spf08.hubspotemail.net
  • include: mailgun.org
  • ip: 202.133.119.11

Threat-feed evidence

History

Related pages

Pivot from kanaloco.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: "kanaloco.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.