Skip to content

Hostname

wellzcare.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of wellzcare.com owner
Contact emails
0efaade3-bde8-4652-b724-6c98ad61995a@identity-protect.org, 21056f87-f220-4bb9-b1fc-f02bb0f255c9@identity-protect.org, 9cf593c5-c712-43df-8073-dec0b5fe0f9e@identity-protect.org, bb522917-ff1b-42b8-bb97-f198cde44b18@identity-protect.org, f8d03534-b0ce-406f-aa16-8a3db2b85b99@identity-protect.org, owner-3266145@wellzcare.com.whoisprivacyservice.org, owner-3388583@wellzcare.com.whoisprivacyservice.org

Subdomains

Subdomain
em8785.wellzcare.com
emotionalhealth.wellzcare.com
mail.wellzcare.com
saudeemocional.wellzcare.com

Showing 4 of 9. View all subdomains →

Mail and authentication

Nameservers

  • ns-44.awsdns-05.com
  • ns-869.awsdns-44.net
  • ns-1239.awsdns-26.org
  • ns-1597.awsdns-07.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
  • ycnm6424z34weixooisls3akjrdcjbo5bmht27m7qrkxtxm7235q.mx-verification.google.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: em8785.wellzcare.com
  • include: em5270.mail.wellzcare.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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