Skip to content

Hostname

heartex.com

Last fetched

heartex.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. heartex.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 · heartex.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/heartex.com

Resolution chain

No IPv4 resolution is recorded for heartex.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of heartex.com owner
Contact emails
ehren305@gmail.com, 3b6f5642-635c-4962-88a6-719a0e45552f@identity-protect.org, 3d242c78-2438-4229-b4c3-748c21de707f@identity-protect.org, 70b2c96d-d0d0-4973-9cce-41c8e64aec51@identity-protect.org, 9bca23c4-5032-46dc-97da-a2c64a6dd7f9@identity-protect.org, a262d243-5667-4462-98bd-942e2a987e24@identity-protect.org, fbf06544-b941-4bce-9b1d-06c042df9200@identity-protect.org, owner-10842589@heartex.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-253.awsdns-31.com
  • ns-806.awsdns-36.net
  • ns-1496.awsdns-59.org
  • ns-2002.awsdns-58.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
  • qfjrly523aneebvz3r7kr56i62nam6o4nznk6pofd7xwj4gyt73q.mx-verification.google.com

SPF policy

  • include: _spf.google.com
  • include: 7539937.spf02.hubspotemail.net
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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