Skip to content

Hostname

amanofd.jp

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
asahi group foods,
Contact emails
domain-adm@n-ais.co.jp, no-kobayashi@amanofoods.co.jp, isp@mark-i.jp

Subdomains

Subdomain
ssc.amanofd.jp
sub-org-sp.amanofd.jp
sub.amanofd.jp
www-org.amanofd.jp
www.amanofd.jp

Showing 5 of 5 subdomains (5 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-290.awsdns-36.com
  • ns-730.awsdns-27.net
  • ns-1107.awsdns-10.org
  • ns-1572.awsdns-04.co.uk

MX records

  • cluster1.us.messagelabs.com
  • cluster1a.us.messagelabs.com

SPF policy

  • ip: 211.128.107.171/32
  • include: spf.mta.hdems.com
  • include: spf.protection.outlook.com
  • include: spf.bserver.jp
  • include: spf-bma.mpme.jp
  • include: e-grant.ko-sokumail.net
  • ip: 13.230.22.195
  • ip: 203.180.101.52
  • ip: 203.180.101.53
  • ip: 203.180.101.82
  • ip: 203.180.101.83
  • ip: 210.134.58.25
  • ip: 52.68.63.166
  • ip: 54.238.9.169
  • ip: 58.138.136.33
  • ip: 58.138.136.34

Threat-feed evidence

History

Related pages

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