defense.direct

Threat posture

Threat feeds listing this

0

Verdict coverage

known-clean

Nutrition Label

Resolution chain

• 172.233.221.214

  172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 172.234.199.15

  172.234.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 172.237.145.27

  172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 188.114.96.3

  188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA

• 188.114.97.3

  188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA

• 35.213.203.121

  35.213.192.0/18 · GOOGLE - Google LLC · Sydney, AU

IPv6 resolution

• 2606:4700:3034::6815:3a7d
• 2606:4700:3036::ac43:cc0b
• 2a06:98c1:3120::3
• 2a06:98c1:3121::3

Attribution

WHOIS identity

Registrar

iana:1479

Registrant organisation

domains by proxy,

Contact emails

defense.direct@domainsbyproxy.com, support@enqode.com, pwp-167514659b8e84bb3dedff30659f96a1@privacyguardian.org

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

Threat-feed evidence

History

Related pages

Pivot from defense.direct into the addresses, networks and registries it depends on.

• Whisper Internet Directory · Home
• TLD · .com
• Live MOAS conflicts
• IP address · 172.233.221.214
• Prefix · 172.233.208.0/20
• Network · AKAMAI-LINODE-AP - Akamai Connected Cloud
• TLD · .direct
• Registrar · iana:1479
• Glossary · What is a hostname?

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "defense.direct"})-[: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.