Skip to content

Hostname

kensetsu-cloud.jp

Last fetched

kensetsu-cloud.jp resolves to 27.82.109.144, announced in 27.82.0.0/16 by KDDI - KDDI CORPORATION in JP. kensetsu-cloud.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 · kensetsu-cloud.jpRouting diversity1.5/10Peering density9.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/kensetsu-cloud.jp

Resolution chain

IPv6 resolution

No AAAA record for kensetsu-cloud.jp is recorded in WhisperGraph.

Attribution

kddi

ORIGIN_AS

WHOIS identity

Registrant organisation
daitec co.,ltd.
Contact emails
info-idc@daitec.co.jp

Subdomains

Subdomain
ap.kensetsu-cloud.jp
apb.kensetsu-cloud.jp
apb1.kensetsu-cloud.jp
ape.kensetsu-cloud.jp
apg.kensetsu-cloud.jp
apk.kensetsu-cloud.jp
dev1.kensetsu-cloud.jp
dev2.kensetsu-cloud.jp
dev3.kensetsu-cloud.jp
dev4.kensetsu-cloud.jp
dx1.kensetsu-cloud.jp
mrc-lp.kensetsu-cloud.jp

Showing 12 of 13. 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.daitec.co.jp
  • dns2.daitec.co.jp
  • dns3.daitec.co.jp
  • ns12.pwd.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

  • mx-gw1.daitec.co.jp
  • mx-gw2.daitec.co.jp
  • mx-gw3.daitec.co.jp
  • mx-gw4.daitec.co.jp
  • mx-gw5.daitec.co.jp

Threat-feed evidence

History

Related pages

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