Skip to content

Hostname

hmco.jp

Last fetched

hmco.jp resolves to 202.218.202.29, announced in 202.218.128.0/17 by IDCF - IDC Frontier Inc. in JP. hmco.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 · hmco.jpRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/hmco.jp

Resolution chain

IPv6 resolution

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

Attribution

idc frontier

ORIGIN_AS

WHOIS identity

Registrant organisation
horsemen kaigi co.,ltd.
Contact emails
domain@hmco.jp

Subdomains

Subdomain
a1.hmco.jp
f1.hmco.jp
mb.hmco.jp
mx.hmco.jp
mx2.hmco.jp
mx3.hmco.jp
pc-cache.hmco.jp
sp-f.hmco.jp
ssl.hmco.jp
sub.hmco.jp
wildcard.hmco.jp
www-f.hmco.jp

Showing 12 of 14. View all subdomains →

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

  • ns01.idcfcloud.com
  • ns02.idcfcloud.com
  • ns03.idcfcloud.com
  • 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

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
  • ip: 202.218.202.27
  • ip: 202.218.202.29
  • ip: 202.230.172.143
  • ip: 210.129.191.16
  • ip: 210.152.246.21

Threat-feed evidence

History

Related pages

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