Skip to content

Hostname

hato.co.jp

Last fetched

hato.co.jp resolves to 18.177.235.167, announced in 18.176.0.0/15 by AMAZON-02 - Amazon.com, Inc. in JP. hato.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 · hato.co.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/hato.co.jp

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for hato.co.jp. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
autodiscover.hato.co.jp
backup.hato.co.jp
mail.hato.co.jp
online.hato.co.jp
preview.hato.co.jp
staging.hato.co.jp
www.hato.co.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-371.awsdns-46.com
  • ns-652.awsdns-17.net
  • ns-1180.awsdns-19.org
  • ns-1648.awsdns-14.co.uk

MX records

  • hato-co-jp.mail.protection.outlook.com

SPF policy

  • include: _spf.hostedemail.com
  • include: spf.protection.outlook.com
  • include: shops.shopify.com
  • include: spf.besender.jp
  • include: spf.bmv.jp
  • ip: 219.111.16.26

Threat-feed evidence

History

Related pages

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