Security
How I protect this site, and how to report a vulnerability if you find one.
Last updated: November 2, 2026.
How I protect the site
- Always encrypted: all traffic goes over HTTPS. Unencrypted connections are redirected, and browsers remember to use HTTPS (HSTS).
- No open ports: the server exposes no ports to the internet; the site is published through an encrypted tunnel.
- Closed admin panel: the site’s admin can’t be reached from the internet.
- Security headers: a content security policy (CSP), protection against the site being embedded in other pages, and browser permissions that aren’t needed (camera, microphone, location) are blocked.
- Protected form: data is validated on the server and there’s a bot filter.
- Minimal data: I only ask for what I need to reply to you.
- Automatic backups and up-to-date software.
Reporting a vulnerability
If you find a security issue on freidergandica.com, email me at [email protected] with the subject “Security”. Please include:
- What you found and where (the URL).
- Steps to reproduce it.
- The impact you think it has.
My commitment
- Confirm I received your report within 5 business days.
- Keep you updated while I fix it.
- Credit you publicly once it’s resolved, if you’d like.
Rules for research
- Act in good faith: don’t access, modify or delete other people’s data.
- No denial-of-service testing, spam or social engineering.
- Give me reasonable time to fix the issue before making it public.
If you follow these rules, I won’t take legal action against you for your research. This site has no paid bug bounty program.
Scope
This policy covers freidergandica.com and www.freidergandica.com. Portfolio projects belong to their clients: if you find something in one of them, email me and I’ll put you in touch with the right people.
The same information is available in standard format (RFC 9116) at /.well-known/security.txt.