B+
salt.security
88/100
1
Add missing security headers (X-Content-Type-Options, Referrer-Policy, Permissions-Policy)
1–2 hours

3 of 5 recommended security headers are missing on salt.security: X-Content-Type-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.

PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1Add: X-Content-Type-Options: nosniff
2Add: Referrer-Policy: strict-origin-when-cross-origin
3Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4Verify with: curl -sI https://salt.security | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2). Issues: DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 include:_spf.google.com include:mktomail.com include:mailgun.org include:mail.zendesk.com inc
Security Headers
2/5 present
Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 48 days remaining; Issued by Google Trust Services.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns3ghw.name.com., ns4kpx.name.com., ns1mpz.name.com., ns2fgv.name.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.