Skip to content

Hostname

testing.api.myleodsc.cloud

Last fetched

testing.api.myleodsc.cloud resolves to 75.2.124.64, announced in 75.2.112.0/20 by AMAZON-02 - Amazon.com, Inc. in US. testing.api.myleodsc.cloud 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 · testing.api.myleodsc.cloudRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/testing.api.myleodsc.cloud

Resolution chain

IPv6 resolution

No AAAA record for testing.api.myleodsc.cloud is recorded in WhisperGraph.

Attribution

Aws

cloud · MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for testing.api.myleodsc.cloud. 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.

Mail and authentication

Nameservers

  • ns-232.awsdns-29.com
  • ns-903.awsdns-48.net
  • ns-1505.awsdns-60.org
  • ns-1577.awsdns-05.co.uk

MX records

  • testing.api.myleodsc.cloud

Threat-feed evidence

History

Related pages

Pivot from testing.api.myleodsc.cloud 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: "testing.api.myleodsc.cloud"})-[: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.