Skip to content

Hostname

cmnh.org

Last fetched

cmnh.org resolves to 67.225.209.28, announced in 67.225.128.0/17 by LIQUIDWEB - Liquid Web, L.L.C in US. cmnh.org 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 · cmnh.orgRouting diversity1.5/10Peering density5.1/10MOAS conflict⚠ 1 conflictThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/cmnh.org

Resolution chain

IPv6 resolution

No AAAA record for cmnh.org is recorded in WhisperGraph.

Attribution

liquid

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Contact emails
a95cj6dr7jr@networksolutionsprivateregistration.com, br8e28me9jj@networksolutionsprivateregistration.com, bs26v5k462m@networksolutionsprivateregistration.com, cw8tu6rp3jg@networksolutionsprivateregistration.com, hc2xm8fd3e7@networksolutionsprivateregistration.com, ry4qv7dc4jq@networksolutionsprivateregistration.com, uy39b66q6j9@networksolutionsprivateregistration.com, w43gw7484p4@networksolutionsprivateregistration.com, w768c7wp3td@networksolutionsprivateregistration.com, wb3qh4ju5y8@networksolutionsprivateregistration.com, xs5ad49q6rm@networksolutionsprivateregistration.com, yn8xm28857a@networksolutionsprivateregistration.com

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

  • elliott.ns.cloudflare.com
  • kimora.ns.cloudflare.com

MX records

  • cmnh-org.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf-us.emailsignatures365.com
  • include: spf.protection.outlook.com
  • include: outboundmail.blackbaud.net
  • include: servers.mcsv.net
  • a: cmnh.org
  • mx: cmnh.org
  • ip: 69.54.55.158

Threat-feed evidence

History

Related pages

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