Skip to content

Hostname

spacecom.mil

Last fetched

spacecom.mil is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. spacecom.mil 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 · spacecom.milRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.0/10canon.whisper.security/host/spacecom.mil

Resolution chain

No IPv4 resolution is recorded for spacecom.mil in WhisperGraph.

IPv6 resolution

No AAAA record for spacecom.mil is recorded in WhisperGraph.

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for spacecom.mil. 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.

Subdomains

Subdomain
www.spacecom.mil

Showing 1 of 1 subdomain (1 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • dns1.nipr.mil
  • dns2.nipr.mil
  • dns3.nipr.mil
  • dns4.nipr.mil
  • dns5.nipr.mil
  • dns6.nipr.mil
  • gphl2128-na010.usstratcom.mil
  • gphl2128-na011.usstratcom.mil
  • gpsl2152-na008.usstratcom.mil
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

SPF policy

  • include: _spf.eemsg.mail.mil
  • ip: 214.8.148.138

Threat-feed evidence

History

Related pages

Pivot from spacecom.mil 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: "spacecom.mil"})-[: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.