v0rt.com

# ===========================================================================
#  security.txt for ssl.org  (RFC 9116)
#  Deploy at:  https://www.ssl.org/.well-known/security.txt
#  Optional duplicate/redirect:  /security.txt  ->  /.well-known/security.txt
#  Serve over HTTPS, Content-Type: text/plain; charset=utf-8
# ===========================================================================

# --- Required fields -------------------------------------------------------

Contact: mailto:[redacted]@iban.com
Contact: https://www.iban.com/contact
Expires: 2027-06-15T23:59:59.000Z

# --- Recommended fields ----------------------------------------------------

Canonical: https://www.ssl.org/.well-known/security.txt
Preferred-Languages: en, bg

# --- Optional fields (uncomment + point at real, live resources) -----------
# Each URL referenced below MUST resolve, or scanners will flag the file.

#Policy: https://www.ssl.org/security-policy
#Encryption: https://www.ssl.org/.well-known/pgp-key.txt
#Acknowledgments: https://www.ssl.org/hall-of-fame
#Hiring: https://www.iban.com/careers

# ===========================================================================
#  Notes
#  - Contact lines are in order of preference. [redacted]@iban.com is your
#    monitored mailbox; consider also adding a dedicated security@ alias if you
#    want security reports separated from general mail.
#  - "Expires" must be a single ISO 8601 timestamp and SHOULD be < 1 year out.
#    Renew before that date; an expired file is treated as stale.
#  - Canonical points at the www host (your canonical hostname). Serve the file
#    so both ssl.org and www.ssl.org resolve it (your existing redirect handles
#    that if non-www -> www is already in place).
#  - You MAY clearsign this file with PGP (RFC 9116 §2.3).
# ===========================================================================