Skip to content

Hostname

defenseorchestrator.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
cisco systems,
Contact emails
lockhart.dev.ops@cisco.com, 4446b40d-49a4-4c8e-b796-4e85c06d6a4e@identity-protect.org, 5e04cb40-4811-476d-94c9-99dd3cbb38cb@identity-protect.org, 7888e006-36c1-4c0b-8733-b7f57fe9a238@identity-protect.org, d2b9faa8-2bb3-4c55-82b6-98258fb72d58@identity-protect.org, e3f377a6-b721-4e8a-8c47-e3e663f3f7d5@identity-protect.org, ead3b55a-f4de-4496-a9ec-f2e20374175d@identity-protect.org, fbb506ed-4469-4eb0-8ef5-ba9a3588318b@identity-protect.org, owner-10655244@defenseorchestrator.com.whoisprivacyservice.org, owner-7223384@defenseorchestrator.com.whoisprivacyservice.org, owner-8451755@defenseorchestrator.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-358.awsdns-44.com
  • ns-622.awsdns-13.net
  • ns-1480.awsdns-57.org
  • ns-1729.awsdns-24.co.uk

Threat-feed evidence

History

Related pages

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