Security fix guide
Your site is missing some standard security settings
Your web server does not send some of the standard safety settings that browsers look for. These are small server settings, not a sign that your site has been hacked.
Issue ID: SEC-HEADERS-001
Severity: moderate
Impact: Low
Effort: S
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Your web server does not send some of the standard safety settings that browsers look for. These are small server settings, not a sign that your site has been hacked.
Why it matters
Your web server does not send some of the standard safety settings that browsers look for. These are small server settings, not a sign that your site has been hacked. This affects browser trust signals and whether visitors feel safe submitting contact details.
How we detect it
- FreeSiteAudit flags this issue when the rule for SEC-HEADERS-001 fails and the page evidence points to Http headers.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Ask your web designer or host to add the settings listed in this finding. It is one place to edit, usually about 30 minutes.
How to re-check it
- Re-run the scan, or check your response headers with securityheaders.com
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.