Skip to content

Hostname

hmr.jp

Last fetched

hmr.jp resolves to 202.32.41.94, announced in 202.34.9.0/24 by IIJ - Internet Initiative Japan Inc. in JP. hmr.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 · hmr.jpRouting diversity1.5/10Peering density9.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.6/10canon.whisper.security/host/hmr.jp

Resolution chain

IPv6 resolution

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

Attribution

iij initiative japan

ORIGIN_AS

WHOIS identity

Registrant organisation
huit
Contact emails
shiroguchi-k@a-net.com, omori-m@huit.co.jp

Subdomains

Subdomain
image.hmr.jp
search.hmr.jp
voice.hmr.jp
www.hmr.jp

Showing 4 of 4 subdomains (4 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-15.awsdns-01.com
  • dns01.netsurf.ad.jp
  • dns02.netsurf.ad.jp
  • ns-1004.awsdns-61.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-1115.awsdns-11.org
  • ns-1579.awsdns-05.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
  • include: spf.ecbeing.co.jp
  • ip: 210.188.202.239
  • ip: 210.188.202.242

Threat-feed evidence

History

Related pages

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