mirror of
https://github.com/hanzo-apps/hanzo.ai.git
synced 2026-10-30 14:58:08 +00:00
zeekayandHanzo Dev
4607e6b8a9
The security page has said to mail [email protected] for a while. Nothing machine-readable said so, and /.well-known/security.txt answered 404, which is where a researcher and every automated scanner look first. RFC 9116, five fields, no signature. Expires is required by the spec and is a year out, so a stale file reads as stale rather than as current. Worth knowing for the sibling sites: lux.network appears to have one already -- the URL returns 200 -- but the body is the Next.js app shell, not a text file. A SPA catch-all answers every path, so 404 is the only honest way to learn this is missing and none of these sites give it. Co-authored-by: Hanzo Dev <[email protected]>
12 lines
415 B
Plaintext
12 lines
415 B
Plaintext
# Hanzo AI — how to report a security problem.
|
|
#
|
|
# RFC 9116. Machine-readable on purpose: scanners and researchers look here
|
|
# first, and a site without this file gets reported to whatever address someone
|
|
# can guess, or not at all.
|
|
|
|
Contact: mailto:[email protected]
|
|
Expires: 2027-08-01T00:00:00.000Z
|
|
Preferred-Languages: en
|
|
Canonical: https://hanzo.ai/.well-known/security.txt
|
|
Policy: https://hanzo.ai/security
|