Skip to content

Hostname

kestramedical.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
1b90bbcc-8c27-44d3-9d2f-45abfe74d140@identity-protect.org, 254b3e24-c7f4-41fd-9134-9f0795d2f193@identity-protect.org, 616ddf78-117b-4397-b088-eb09b47dcaca@identity-protect.org, 8c386f09-cd7d-4f5c-a524-36f4ec734296@identity-protect.org, 9b0d3b17-a228-4851-93bf-e9f5d17d288c@identity-protect.org, ca63e1b4-15ea-455d-8b05-08894ef7f297@identity-protect.org, owner-8214467@kestramedical.com.whoisprivacyservice.org, owner@kestramedical.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-280.awsdns-35.com
  • ns-822.awsdns-38.net
  • ns-1230.awsdns-25.org
  • ns-1745.awsdns-26.co.uk

MX records

  • kestramedical-com.mail.protection.outlook.com

SPF policy

  • include: spf.emailsignatures365.com
  • include: _spf.kestramedical.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: _spf.atlassian.net
  • include: 19560847.spf03.hubspotemail.net
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

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