Skip to content

Hostname

heroes.eu

Last fetched

heroes.eu resolves to 199.60.103.6, announced in 199.60.103.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in US. heroes.eu 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 · heroes.euRouting diversity2.4/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/heroes.eu

Resolution chain

IPv6 resolution

No AAAA record for heroes.eu is recorded in WhisperGraph.

Attribution

cloudflare london

ORIGIN_AS

WHOIS identity

Registrar
registrar:registrygate gmbh

Subdomains

Subdomain
_dmarc.heroes.eu
_mta-sts.heroes.eu
a.heroes.eu
admin.heroes.eu
api.heroes.eu
app.heroes.eu
autoconfig.heroes.eu
autodiscover.heroes.eu
b.heroes.eu
bbs.heroes.eu
beta.heroes.eu
blog.heroes.eu

Showing 12 of 245. 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

  • anexia.secondns.at
  • anexia.firstns.cc
  • anexia.fifthns.com
  • anexia.thirdns.de
  • 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
  • anexia.fourthns.systems

MX records

  • heroes-eu.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: _spf.recruiting-portal.com
  • include: spf.tantum-it.de
  • include: 26117705.spf10.hubspotemail.net
  • ip: 217.91.68.162
  • ip: 62.154.216.253

Threat-feed evidence

History

Related pages

Pivot from heroes.eu 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: "heroes.eu"})-[: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.