Hostname
clamsnet.org
Last fetched
clamsnet.org resolves to 104.16.168.230, announced in 104.16.160.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. clamsnet.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.16.168.230
104.16.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for clamsnet.org is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- clams, inc. (cape libraries automated materials sharing)
- Contact emails
- cy9dm7j83ze@networksolutionsprivateregistration.com, de5zj9p57cm@networksolutionsprivateregistration.com, n33n72nz5rp@networksolutionsprivateregistration.com, pa47n6fx4s6@networksolutionsprivateregistration.com, s366f7bn3k3@networksolutionsprivateregistration.com, up4ks9mb632@networksolutionsprivateregistration.com, vt86z2d82dr@networksolutionsprivateregistration.com, x55ka2yu6md@networksolutionsprivateregistration.com
Subdomains
Showing 12 of 45. View all 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
- ns-84.awsdns-10.com
- ns-950.awsdns-54.net
- 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
- ns-1370.awsdns-43.org
- ns-1691.awsdns-19.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from clamsnet.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: "clamsnet.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.