Skip to content

Hostname

konami.jp

Last fetched

konami.jp resolves to 67.199.248.12, announced in 67.199.248.0/24 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. konami.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 · konami.jpRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.6/10canon.whisper.security/host/konami.jp

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
clarivate analytics (japan) co.,ltd.
Contact emails
domain.jp@markmonitor.com, admin@thomsonbrandy.jp

Subdomains

Subdomain
_spf-a.konami.jp
_spf-b.konami.jp
akazukin.konami.jp
amdriver.konami.jp
busou.konami.jp
dl.konami.jp
ea-pass.konami.jp
foodforce.konami.jp
game.konami.jp
gokujo.konami.jp
hanapoo.konami.jp
kids-smile.konami.jp

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

  • a1-2.akam.net
  • a13-66.akam.net
  • a20-64.akam.net
  • a26-66.akam.net
  • a4-64.akam.net
  • a7-65.akam.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

SPF policy

  • include: _spf-a.konami.jp
  • include: _spf-b.konami.jp

Threat-feed evidence

History

Related pages

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