Skip to content

Hostname

army.mil.ph

Last fetched

army.mil.ph resolves to 104.26.6.119, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. army.mil.ph 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 · army.mil.phRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/army.mil.ph

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

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

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

  • diana.ns.cloudflare.com
  • vicente.ns.cloudflare.com
  • 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

MX records

  • alt1.us.email.fireeyecloud.com
  • alt2.us.email.fireeyecloud.com
  • alt3.us.email.fireeyecloud.com
  • primary.us.email.fireeyecloud.com
  • mail.army.mil.ph
  • pmx.army.mil.ph

SPF policy

  • include: _spf.fireeyecloud.com
  • a: army.mil.ph
  • mx: army.mil.ph
  • a: mail.army.mil.ph
  • ip: 121.58.209.211
  • ip: 121.58.209.212
  • ip: 126.209.81.25

Threat-feed evidence

History

Related pages

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