Skip to content

Hostname

shadowhealth.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:447
Registrant organisation
domains by proxy,
Contact emails
shadowhealth.com@domainsbyproxy.com, 15j6h7kz12wd@idp.email, b6c780e8f12f3c33f22e2f13c096275e-4253078@contact.gandi.net

Subdomains

Subdomain
app.shadowhealth.com
bookstore-staging.shadowhealth.com
dev.shadowhealth.com
harm-staging.shadowhealth.com
link.shadowhealth.com
nonprod.shadowhealth.com
pilot.shadowhealth.com
prod.shadowhealth.com
reminder.shadowhealth.com
rubric-staging.shadowhealth.com
rubric.shadowhealth.com
sandboxa.shadowhealth.com

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

Mail and authentication

Nameservers

  • ns-157.awsdns-19.com
  • ns-516.awsdns-00.net
  • ns-1333.awsdns-38.org
  • ns-1961.awsdns-53.co.uk

MX records

  • shadowhealth-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: aspmx.pardot.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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