Skip to content

Hostname

sakura-forest.com

Last fetched

sakura-forest.com resolves to 13.226.69.37, announced in 13.226.69.0/24 by AMAZON-02 - Amazon.com, Inc. in HK. sakura-forest.com 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 · sakura-forest.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/sakura-forest.com

Resolution chain

IPv6 resolution

No AAAA record for sakura-forest.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:49
Registrant organisation
cocosys,
Contact emails
privacy@whoisprivacyprotection.info, komaji@sakuraforest.co.jp, nishio@cocosys.co.jp

Subdomains

Subdomain
a8cv.sakura-forest.com
cms.sakura-forest.com
crm.sakura-forest.com
eads.sakura-forest.com
img.sakura-forest.com
sb.sakura-forest.com
stg-cms.sakura-forest.com
stg-crm.sakura-forest.com
stg.sakura-forest.com
www.sakura-forest.com

Showing 10 of 10 subdomains (10 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-178.awsdns-22.com
  • ns-1000.awsdns-61.net
  • ns-1404.awsdns-47.org
  • ns-2029.awsdns-61.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • mx: sakura-forest.com
  • include: fc18209.cn-5738.jp

Threat-feed evidence

History

Related pages

Pivot from sakura-forest.com 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: "sakura-forest.com"})-[: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.