Skip to content
https://fpf.org

Security

· 13 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
75
GRADE
C
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
Content Security Policy
Action
3 of 10 CSP checks passed
FIX
3 of 10 CSP checks passed
Info::
Raw CSP policy
Got: default-src 'none'; connect-src 'self' 'unsafe-inline' https://cdn.cookielaw.org/ https://cdn-cookieyes.com/ https://directory.cookieyes.com/ https://www.google-analytics.com/ https://*.facebook.com/ https://geolocation.onetrust.com/ https://fpf.org/ https://www.cloudflare.com/ https://vimeo.com/ https://log.cookieyes.com/; font-src 'self' data: https://cdnjs.cloudflare.com/ https://*.google.com/ https://*.typekit.net/ https://fonts.gstatic.com/; img-src 'self' data: https://*.gravatar.com/ https://*.ytimg.com/ https://*.gstatic.com/ https://*.google.com/ https://www.google-analytics.com/ https://fpf.org/ https://img.youtube.com/ https://i.vimeocdn.com/ https://cdn-cookieyes.com/; frame-src 'self' https://www.youtube-nocookie.com/ https://*.twitter.com/ https://*.google.com/ https://*.facebook.com https://*.youtube.com https://*.eventbrite.com/ https://player.vimeo.com/; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net/ https://cdnjs.cloudflare.com/ https://*.gstatic.com/ https://*.google.com/ https://*.typekit.net/ https://fonts.googleapis.com/; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net/ https://cdn.cookielaw.org/ https://ajax.googleapis.com/ https://www.googletagmanager.com/ https://www.google-analytics.com/ https://*.twitter.com/ https://*.gstatic.com/ https://*.google.com/ https://*.eventbrite.com/ https://*.youtube.com/ https://fpf.org/ https://player.vimeo.com/ https://*.vimeocdn.com/ https://cdn-cookieyes.com/ https://*.cookieyes.com/; worker-src 'self' https://*.youtube.com/ https://*.vimeo.com/ blob:; block-all-mixed-content;
Info::
default-src directive is set
Got: default-src 'none'
Critical::
'unsafe-inline' found in script source
'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
Got: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net/ https://cdn.cookielaw.org/ https://ajax.googleapis.com/ https://www.googletagmanager.com/ https://www.google-analytics.com/ https://*.twitter.com/ https://*.gstatic.com/ https://*.google.com/ https://*.eventbrite.com/ https://*.youtube.com/ https://fpf.org/ https://player.vimeo.com/ https://*.vimeocdn.com/ https://cdn-cookieyes.com/ https://*.cookieyes.com/
Critical::
'unsafe-eval' found in script source
'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
Got: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net/ https://cdn.cookielaw.org/ https://ajax.googleapis.com/ https://www.googletagmanager.com/ https://www.google-analytics.com/ https://*.twitter.com/ https://*.gstatic.com/ https://*.google.com/ https://*.eventbrite.com/ https://*.youtube.com/ https://fpf.org/ https://player.vimeo.com/ https://*.vimeocdn.com/ https://cdn-cookieyes.com/ https://*.cookieyes.com/
Info::
No wildcard in script source
Info::
object-src falls back to default-src
Warning::
base-uri directive is missing
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
Expected: base-uri 'self'
Warning::
frame-ancestors directive is missing
frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
Expected: frame-ancestors 'self'
Warning::
form-action directive is missing
form-action restricts where forms can submit data, preventing form hijacking.
Expected: form-action 'self'
Info::
upgrade-insecure-requests is not set
This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.
Expected: upgrade-insecure-requests

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'
Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests
Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

default-src 'none'
connect-src 'self''unsafe-inline'https://cdn.cookielaw.org/https://cdn-cookieyes.com/https://directory.cookieyes.com/https://www.google-analytics.com/https://*.facebook.com/https://geolocation.onetrust.com/https://fpf.org/https://www.cloudflare.com/https://vimeo.com/https://log.cookieyes.com/
font-src 'self'data:https://cdnjs.cloudflare.com/https://*.google.com/https://*.typekit.net/https://fonts.gstatic.com/
img-src 'self'data:https://*.gravatar.com/https://*.ytimg.com/https://*.gstatic.com/https://*.google.com/https://www.google-analytics.com/https://fpf.org/https://img.youtube.com/https://i.vimeocdn.com/https://cdn-cookieyes.com/
frame-src 'self'https://www.youtube-nocookie.com/https://*.twitter.com/https://*.google.com/https://*.facebook.comhttps://*.youtube.comhttps://*.eventbrite.com/https://player.vimeo.com/
style-src 'self''unsafe-inline'https://cdn.jsdelivr.net/https://cdnjs.cloudflare.com/https://*.gstatic.com/https://*.google.com/https://*.typekit.net/https://fonts.googleapis.com/
script-src 'self''unsafe-inline''unsafe-eval'https://cdn.jsdelivr.net/https://cdn.cookielaw.org/https://ajax.googleapis.com/https://www.googletagmanager.com/https://www.google-analytics.com/https://*.twitter.com/https://*.gstatic.com/https://*.google.com/https://*.eventbrite.com/https://*.youtube.com/https://fpf.org/https://player.vimeo.com/https://*.vimeocdn.com/https://cdn-cookieyes.com/https://*.cookieyes.com/
worker-src 'self'https://*.youtube.com/https://*.vimeo.com/blob:
block-all-mixed-content
F
Subresource Integrity
Action
0 of 9 external resources have SRI
FIX
0 of 9 external resources have SRI
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=G-W21F0NDTW9&cx=c&gtm=4e64k1
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtm.js?id=GTM-T3KLDF7
Warning::
External script from cdn-cookieyes.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn-cookieyes.com/client_data/f130066eff26df77ca6c4fe2/script.js
Warning::
External script from cdn-cookieyes.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn-cookieyes.com/client_data/f130066eff26df77ca6c4fe2/banner.js
Warning::
External link from use.typekit.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://use.typekit.net/kxf6fpd.css?ver=6.9.4
Warning::
External link from cdn.jsdelivr.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.jsdelivr.net/gh/fancyapps/fancybox@3.5.7/dist/jquery.fancybox.min.css
Warning::
External link from cdnjs.cloudflare.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.2/css/all.min.css
Warning::
External script from ajax.googleapis.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js?ver=3.4.1
Warning::
External script from cdn.jsdelivr.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.jsdelivr.net/gh/fancyapps/fancybox@3.5.7/dist/jquery.fancybox.min.js?ver=6.9.4
SRI Coverage 0 / 9 of external resources have integrity hashes
TagDomainIntegrity
<script>www.googletagmanager.com✗ Missing
<script>www.googletagmanager.com✗ Missing
<script>cdn-cookieyes.com✗ Missing
<script>cdn-cookieyes.com✗ Missing
<link>use.typekit.net✗ Missing
<link>cdn.jsdelivr.net✗ Missing
<link>cdnjs.cloudflare.com✗ Missing
<script>ajax.googleapis.com✗ Missing
<script>cdn.jsdelivr.net✗ Missing
D
Email Security
Action
DMARC: none
FIX
DMARC: none
Warning::
DMARC policy is none — monitoring only
This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.
DMARC
Policy none — monitoring only, does not block spoofing Record v=DMARC1;p=none;pct=1;rua=mailto:eb466496d3@rua.easydmarc.us,mailto:admin@fpf.org;ruf=mailto:eb466496d3@ruf.easydmarc.us;fo=1;

This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.

Why this matters

DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.

Learn more ▾

DMARC's three policies are p=none (monitor only), p=quarantine (mark as spam), and p=reject (bounce). Most domains start at p=none to gather data, but stay there forever, leaving spoofers unblocked. After 30 days of clean DMARC reports, graduate to p=quarantine, then p=reject.

Source: DMARC.org / NIST

D
security.txt
Action
No /.well-known/security.txt published
FIX

security.txt

No security.txt found at /.well-known/security.txt

B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
No CORS headers present — secure default
CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control
C
Known vulnerability matches
Action
2 known vulnerability match(es) against detected tech
REVIEW

Known Vulnerabilities

LibraryVersionSeveritySummaryFixed In
jQuery3.4.1mediumpassing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.3.5.0
jQuery3.4.1mediumRegex in its jQuery.htmlPrefilter sometimes may introduce XSS3.5.0
A
Security Headers
8 of 10 headers properly configured
PASS
8 of 10 headers properly configured
Info::
Strict-Transport-Security is properly configured
Got: max-age=31622400; includeSubDomains; preload
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Info::
X-Frame-Options is properly configured
Got: SAMEORIGIN
Info::
Referrer-Policy is properly configured
Got: no-referrer
Info::
Permissions-Policy is set
Got: sync-xhr=*, autoplay=(), accelerometer=(), camera=(), geolocation=self, gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=()
Info::
Content-Security-Policy is present
Got: default-src 'none'; connect-src 'self' 'unsafe-inline' https://cdn.cookielaw.org…
Warning::
Cross-Origin-Opener-Policy header is missing
COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
Expected: same-origin
Warning::
Cross-Origin-Embedder-Policy header is missing
COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
Expected: require-corp
Info::
X-Powered-By header is not present
Info::
Server header is present without version info
Got: cloudflare

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin
Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp
Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

A+
TLS & Certificates
TLS 1.3, 7 checks passed
PASS
TLS 1.3, 7 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_CHACHA20_POLY1305_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 89 days)
Got: 2026-07-21T05:34:49Z
Info::
Certificate chain has 3 certificates
Info::
Certificate uses modern signature algorithm
Got: ECDSA-SHA256
Info::
Certificate covers 2 domain(s)
Got: fpf.org, *.fpf.org
Info::
Certificate is issued by a trusted CA
Got: CN=WE1,O=Google Trust Services,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection
Protocol
TLS 1.3
Cipher Suite
TLS_CHACHA20_POLY1305_SHA256
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=fpf.orgIssuer CN=WE1,O=Google Trust Services,C=USValid 2026-04-22T04:34:59Z → 2026-07-21T05:34:49ZExpires in 89 days SANs fpf.org, *.fpf.orgSignature ECDSA-SHA256Serial 9445a4ffb9b5c47a0ef9bddc769939cd
Intermediate (CA Certificate)
Subject CN=WE1,O=Google Trust Services,C=USIssuer CN=GTS Root R4,O=Google Trust Services LLC,C=USValid 2023-12-13T09:00:00Z → 2029-02-20T14:00:00ZExpires in 1034 days Signature ECDSA-SHA384Serial 7ff31977972c224a76155d13b6d685e3
Intermediate (CA Certificate)
Subject CN=GTS Root R4,O=Google Trust Services LLC,C=USIssuer CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BEValid 2023-11-15T03:43:21Z → 2028-01-28T00:00:42ZExpires in 645 days Signature SHA256-RSASerial 7fe530bf331343bedd821610493d8a1b
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
No security.txt found
Consider adding a security.txt at /.well-known/security.txt.
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✓ Not foundSecurity Policy—
A+
Permissions-Policy
11 directives, 0 missing
PASS
11 directives, 0 missing
Info::
sync-xhr=*
Info::
autoplay=() — blocked for all origins
Info::
accelerometer=() — blocked for all origins
Info::
camera=() — blocked for all origins
Info::
geolocation=self
Info::
gyroscope=() — blocked for all origins
Info::
magnetometer=() — blocked for all origins
Info::
microphone=() — blocked for all origins
Info::
payment=() — blocked for all origins
Info::
usb=() — blocked for all origins
Info::
interest-cohort=() — blocked for all origins

Raw Header

sync-xhr=* autoplay=() accelerometer=() camera=() geolocation=self gyroscope=() magnetometer=() microphone=() payment=() usb=() interest-cohort=()

Feature Permissions

Blocked Self Only Unrestricted Not Set
sync-xhr Unrestricted
autoplay Blocked
accelerometer Blocked
camera Blocked
geolocation Self Only
gyroscope Blocked
magnetometer Blocked
microphone Blocked
payment Blocked
usb Blocked
interest-cohort Blocked
A
Transport Security
HTTP/3, HSTS, and TLS version analysis
PASS
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) not advertised
HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
Info::
HSTS enabled (includeSubDomains, preload)
Info::
HSTS preload enabled
Info::
TLS 1.3 in use (fastest handshake, 1-RTT)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback