Skip to content

Hostname

zero.health

Last fetched

zero.health resolves to 104.154.172.213, announced in 104.154.160.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. zero.health 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 · zero.healthRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/zero.health

Resolution chain

IPv6 resolution

No AAAA record for zero.health is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for zero.health. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
admin.zero.health
api.zero.health
assets.zero.health
auth.zero.health
care.zero.health
config.zero.health
em5604.zero.health
files.zero.health
go.zero.health
inbox.zero.health
login.zero.health
my.zero.health

Showing 12 of 22. 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-413.awsdns-51.com
  • ns-610.awsdns-12.net
  • ns-1521.awsdns-62.org
  • ns-1991.awsdns-56.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.google.com
  • include: mail.zendesk.com
  • include: em5604.zero.health
  • include: 4141657.spf06.hubspotemail.net

Threat-feed evidence

History

Related pages

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