Hostname
christopherwardforum.com
Last fetched
christopherwardforum.com resolves to 104.21.16.121, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. christopherwardforum.com 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.16.121
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.212.86
172.67.208.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
- 78.129.146.44
78.129.128.0/17 · IOMART-AS - IOMART CLOUD SERVICES LIMITED · Maidenhead, GB
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:69
- Registrant organisation
- christopher ward
- Contact emails
- administrator@christopherward.ch, gdpr-masking@gdpr-masked.com, administrator@christopherward.co.uk
Subdomains
| Subdomain |
|---|
| www.christopherwardforum.com |
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.
Mail and authentication
Nameservers
- beau.ns.cloudflare.com
- gigi.ns.cloudflare.com
- ns10.digicertdns.com
- ns11.digicertdns.com
- ns12.digicertdns.com
- ns13.digicertdns.net
- ns14.digicertdns.net
- ns15.digicertdns.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
MX records
- mx1.oraone.nl
SPF policy
- ip: 78.129.146.44
Threat-feed evidence
History
Related pages
Pivot from christopherwardforum.com 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: "christopherwardforum.com"})-[: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.