Skip to content

Hostname

healint.com

Last fetched

healint.com resolves to 108.138.128.127, announced in 108.138.128.0/22 by AMAZON-02 - Amazon.com, Inc. in US. healint.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 · healint.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/healint.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
ali elgamal
Contact emails
7ff33280fa7f7169e1e94fa752de154a-4449305@contact.gandi.net

Subdomains

Subdomain
3e-office-test.healint.com
3e-office.healint.com
analytics.healint.com
aphrodite.healint.com
aristotle.healint.com
bast.healint.com
bat.healint.com
bes.healint.com
bigollo.healint.com
blackberry.healint.com
bloodorange.healint.com
blueberry.healint.com

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

  • ns-469.awsdns-58.com
  • ns-578.awsdns-08.net
  • ns-1267.awsdns-30.org
  • ns-1873.awsdns-42.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: spf.braintreegateway.com
  • include: _spf.google.com
  • a: healint.com
  • mx: healint.com
  • include: squarespace-mail.com

Threat-feed evidence

History

Related pages

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