Skip to content

Hostname

isl.co.jp

Last fetched

isl.co.jp resolves to 163.44.2.127, announced in 163.44.0.0/18 by InfoSphere - NTT PC Communications, Inc. in JP. isl.co.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 · isl.co.jpRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/isl.co.jp

Resolution chain

IPv6 resolution

No AAAA record for isl.co.jp is recorded in WhisperGraph.

Attribution

ntt

ORIGIN_AS

WHOIS identity

Registrant organisation
ichikawa soft laboratory,co.ltd.

Subdomains

Subdomain
edu.isl.co.jp
edum.isl.co.jp
eserver3.isl.co.jp
etest.isl.co.jp
etest2.isl.co.jp
etest3.isl.co.jp
lily01.isl.co.jp
mgate.isl.co.jp
ns.isl.co.jp
racfii.isl.co.jp
shop.isl.co.jp
silkypix.isl.co.jp

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

  • asns1.customer.ne.jp
  • asns2.customer.ne.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

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

SPF policy

  • include: _spf.google.com
  • include: _spf.maildeliver.jp
  • ip: 122.219.46.102
  • ip: 210.231.183.240
  • ip: 210.251.66.227

Threat-feed evidence

History

Related pages

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