Skip to content

Hostname

herocomm.com

Last fetched

herocomm.com resolves to 104.218.12.123, announced in 104.218.8.0/21 by A2HOSTING - A2 Hosting, Inc. in US. herocomm.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 · herocomm.comRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/herocomm.com

Resolution chain

IPv6 resolution

No AAAA record for herocomm.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
as42f6vm5hh@networksolutionsprivateregistration.com, hj6w29dc7ub@networksolutionsprivateregistration.com, jx35d47t33m@networksolutionsprivateregistration.com, k22ra7wj782@networksolutionsprivateregistration.com, w88cj5av5c4@networksolutionsprivateregistration.com

Subdomains

Subdomain
autodiscover.herocomm.com
cpanel.herocomm.com
cpcalendars.herocomm.com
cpcontacts.herocomm.com
mail.herocomm.com
webdisk.herocomm.com
webmail.herocomm.com
www.herocomm.com

Showing 8 of 8 subdomains (8 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

  • ns1.a2hosting.com
  • ns2.a2hosting.com
  • ns3.a2hosting.com
  • ns4.a2hosting.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

  • mail.herocomm.com

Threat-feed evidence

History

Related pages

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