Skip to content

Hostname

jisin.jp

Last fetched

jisin.jp resolves to 13.227.192.114, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. jisin.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 · jisin.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/jisin.jp

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
kiyomitsu komiyama
Contact emails
tech@kobunsha.com

Subdomains

Subdomain
blog.jisin.jp
data.jisin.jp
ib25518.jisin.jp
img.jisin.jp
kgadmin.jisin.jp
login.jisin.jp
panda.jisin.jp
ssfpc.jisin.jp

Showing 8 of 9. 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

  • ns-395.awsdns-49.com
  • ns-723.awsdns-26.net
  • 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
  • ns-1244.awsdns-27.org
  • ns-1775.awsdns-29.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: spf-bma.mpme.jp

Threat-feed evidence

History

Related pages

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