Hostname
psichi.org
Last fetched
psichi.org resolves to 104.20.26.40, announced in 104.20.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. psichi.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.20.26.40
104.20.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 162.159.141.168
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.1.164
172.66.0.0/22 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.169.158
172.66.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for psichi.org is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:886
- Registrant organisation
- domain privacy service fbo registrant.
- Contact emails
- psichi.org@domainprivacygroup.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
- cecelia.ns.cloudflare.com
- remy.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
- psichi-org.mail.eo.outlook.com
- psichi-org.mail.protection.outlook.com
SPF policy
- ip: 24.73.102.0/24
- include: _spf.createsend.com
- mx: psichi-org.mail.eo.outlook.com
- mx: psichi-org.mail.protection.outlook.com
- include: spf.protection.outlook.com
- ip: 24.73.102.105
- ip: 24.73.102.106
- ip: 24.73.102.112
- ip: 24.73.102.113
- ip: 66.18.33.202
- ip: 66.18.33.204
Threat-feed evidence
History
Related pages
Pivot from psichi.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: "psichi.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.