Skip to content

Hostname

g-shock.jp

Last fetched

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

Resolution chain

IPv6 resolution

No AAAA record for g-shock.jp is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Contact emails
domain@casio.co.jp

Subdomains

Subdomain
mr-g.g-shock.jp
products.g-shock.jp
ryo.g-shock.jp
smetrics.g-shock.jp
spf001.g-shock.jp
spf002.g-shock.jp
www.g-shock.jp

Showing 7 of 7 subdomains (7 per page).

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-160.awsdns-20.com
  • ns-546.awsdns-04.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-1438.awsdns-51.org
  • ns-1827.awsdns-36.co.uk

MX records

  • inbound-smtp.ap-northeast-1.amazonaws.com
  • mnm1.casio.jp

SPF policy

  • include: fc1840.cuenote.jp
  • include: spf001.g-shock.jp
  • include: spf002.g-shock.jp

Threat-feed evidence

History

Related pages

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