Skip to content

Hostname

sentinel.leanserver.com

Last fetched

sentinel.leanserver.com resolves to 16 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.

Nutrition Label

WHISPER CANON · sentinel.leanserver.comRouting diversity5.4/10Peering density9.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint0.0/10canon.whisper.security/host/sentinel.leanserver.com

Resolution chain

sentinel.leanserver.com resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
16.15.179.11316.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.183.10716.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.186.4516.15.184.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.192.17016.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.192.4316.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.194.24716.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.195.20816.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
3.5.20.903.5.20.0/24AS14618AMAZON-AES - Amazon.com, Inc.US
52.216.43.4552.216.32.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.216.51.13352.216.48.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.166.22152.217.160.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.228.18952.217.224.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.235.24552.217.224.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.92.13952.217.92.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.99.6752.217.96.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
54.231.134.10154.231.128.0/19AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

No WHOIS records are currently associated with sentinel.leanserver.com in WhisperGraph.

Subdomains

1 observed subdomain of sentinel.leanserver.com.

Subdomain
endpoint.sentinel.leanserver.com

Threat posture

History

Related pages

Pivot deeper into the graph from sentinel.leanserver.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "sentinel.leanserver.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.