Hostname
nmc.org
Last fetched
nmc.org resolves to 104.21.73.117, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. nmc.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.73.117
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.162.69
172.67.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 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
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- laurence johnson
- Contact emails
- an9ht2eh3hb@networksolutionsprivateregistration.com, b85443ab3c7@networksolutionsprivateregistration.com, dm63h5wz5kg@networksolutionsprivateregistration.com, gh2jx9366gm@networksolutionsprivateregistration.com, gq4e69cg8z9@networksolutionsprivateregistration.com, tu5d68jy5sg@networksolutionsprivateregistration.com, vu9uf4w86qp@networksolutionsprivateregistration.com, w384u3bz6g6@networksolutionsprivateregistration.com, wg7td7eb373@networksolutionsprivateregistration.com, wx8nz8re36m@networksolutionsprivateregistration.com, xe36m3eq6w6@networksolutionsprivateregistration.com, zc9ud5w66mu@networksolutionsprivateregistration.com, zz82f56v3wr@networksolutionsprivateregistration.com, johnson@newmediacenters.org, website@nmc.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
- robin.ns.cloudflare.com
- scott.ns.cloudflare.com
MX records
- mx1.improvmx.com
- mx2.improvmx.com
SPF policy
- include: servers.mcsv.net
Threat-feed evidence
History
Related pages
Pivot from nmc.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: "nmc.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.