Skip to content
https://facebook.com

Security

· 32 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
81
GRADE
B
FIX
5
REVIEW
7
PASS
20
INFO
0
Checks
32
20 PASS 7 REVIEW 5 FIX
F
Security Headers
Action
2 of 10 headers properly configured
FIX
2 of 10 headers properly configured
Warning::
HSTS max-age is too short (15552000s, should be ≥ 31536000s)
A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).
Got: max-age=15552000; preload Expected: max-age=31536000; includeSubDomains
Warning::
X-Content-Type-Options header is missing
This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
Expected: nosniff
Warning::
X-Frame-Options header is missing
This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
Expected: DENY
Warning::
Referrer-Policy header is missing
Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
Expected: strict-origin-when-cross-origin
Warning::
Permissions-Policy header is missing
Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
Expected: geolocation=(), camera=(), microphone=()
Critical::
Content-Security-Policy header is missing
CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
Expected: default-src 'self'
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 not present
Info::
Domain is in the Chrome HSTS preload list (status: preloaded)
Got: preloaded

CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.

Expected: default-src 'self'
Why this matters

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies or rewrite the page is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever.

Source: OWASP / MDN

A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).

Expected: max-age=31536000; includeSubDomains
Why this matters

Short HSTS max-age leaves a downgrade-attack window every time the cache expires — set ≥ 1 year.

Learn more ▾

max-age below 31536000 (1 year) is below industry recommendation. The browser forgets the HSTS policy and re-exposes first-visit downgrade attacks. Set to 63072000 (2 years) and add `includeSubDomains; preload` to qualify for the HSTS preload list.

Source: RFC 6797 / hstspreload.org

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff
Why this matters

MIME sniffing lets browsers run uploaded files as JavaScript, turning a file upload into an XSS.

Learn more ▾

Setting X-Content-Type-Options: nosniff tells browsers to trust your declared Content-Type instead of guessing. Without it, an attacker who uploads a polyglot file can sometimes get it executed as a script. One header, no downside.

Source: OWASP / MDN

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY
Why this matters

Without frame protection, your site can be embedded in a hostile page and used for clickjacking.

Learn more ▾

Clickjacking overlays your site under a transparent malicious page so users click invisible buttons. Setting X-Frame-Options: DENY (or a modern frame-ancestors CSP directive) blocks the embedding entirely. There's almost never a legitimate reason to allow it.

Source: OWASP / MDN

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin
Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()
Why this matters

Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.

Learn more ▾

By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.

Source: MDN / W3C

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

F
Content Security Policy
Action
No enforcing CSP policy found
FIX
No enforcing CSP policy found
Critical::
No Content-Security-Policy header found
CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.
Expected: default-src 'self'

CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

Expected: default-src 'self'
Why this matters

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever. Start in Report-Only mode, fix violations, then graduate to enforcing.

Source: OWASP / MDN

F
Subresource Integrity Adoption
Action
0% SRI adoption (0/13 third-party resources)
FIX
0% SRI adoption (0/13 third-party resources)
Warning::
SRI adoption: 0/13 third-party resources protected (0%)
Of 13 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource. Missing SRI on (first 5 examples): - https://static.xx.fbcdn.net/rsrc.php/v5/yh/l/0,cross/6M8CLqSinCY0-ET_2exAhl7TF2-QXH5TPT9DWDYPz6DhfgQe914iiBfvP3p6y_S61oONMKn3YhINqU49pVNahkCkvx2I9b7Pb8K.css - https://static.xx.fbcdn.net/rsrc.php/v4/yh/r/L1turxb8Ua5.js - https://static.xx.fbcdn.net/rsrc.php/v4iFbC4/yx/l/en_US-j/x3v8UspWx-c-k8LMvdap7sSMdaQqgTEV2WJ3XzkWlmd_v_kkAv_-wGQgXdYivvCwsHHKy1uKLQ_0jLSF6kN-2GoifAozIMNFBkkw1JtOGoHMq0nyQSP3ZLAfTu4yAsukPWHDic65UqSjJilsVjQqltBeBhusk2amyJhKMh2otzgdunJl3g9q4pR78qL69VqNNp4Gm1BHl-lElGzTH4Lah-t55E7mOl6Gkjq0OVeavkZc4HIHnCJZCcc2ZP1Mq8wypiAW_bfk-AMUuK2ufRhAdmh5DEndjkC1LYw5WWi7IP1HIUYBqZ4h.js - https://static.xx.fbcdn.net/rsrc.php/v4iZ9D4/yt/l/en_US-j/fstkMPXuEgz.js - https://static.xx.fbcdn.net/rsrc.php/v4i_054/yq/l/en_US-j/kM6t6qdJVbH.js Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.
Got: 0% (0/13)
F
Subresource Integrity
Action
0 of 13 external resources have SRI
FIX
0 of 13 external resources have SRI
Warning::
External link from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v5/yh/l/0,cross/6M8CLqSinCY0-ET_2exAhl7TF2-QXH5TPT9DWDYPz6DhfgQe914iiBfvP3p6y_S61oONMKn3YhINqU49pVNahkCkvx2I9b7Pb8K.css
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4/yh/r/L1turxb8Ua5.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4iFbC4/yx/l/en_US-j/x3v8UspWx-c-k8LMvdap7sSMdaQqgTEV2WJ3XzkWlmd_v_kkAv_-wGQgXdYivvCwsHHKy1uKLQ_0jLSF6kN-2GoifAozIMNFBkkw1JtOGoHMq0nyQSP3ZLAfTu4yAsukPWHDic65UqSjJilsVjQqltBeBhusk2amyJhKMh2otzgdunJl3g9q4pR78qL69VqNNp4Gm1BHl-lElGzTH4Lah-t55E7mOl6Gkjq0OVeavkZc4HIHnCJZCcc2ZP1Mq8wypiAW_bfk-AMUuK2ufRhAdmh5DEndjkC1LYw5WWi7IP1HIUYBqZ4h.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4iZ9D4/yt/l/en_US-j/fstkMPXuEgz.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4i_054/yq/l/en_US-j/kM6t6qdJVbH.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4iJVq4/y5/l/en_US-j/UnZ-EVl6pqh.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4ivN34/y8/l/en_US-j/6b8g-QgQ3_YC9j9W8O4uJ3WJukooR-9NvNR8emwuUeOHCrtbZ7I8rJDRi7mWBMSxEcjMVGcktGGRp72OqDwSuA8Ya7eSNpDNxgKVIPNHOqVL96GSBvj8_FEnWhlOg4ZYKX0hePZ2GqKu-kUqm8HXN6FrYZ.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4iw5g4/ya/l/en_US-j/V15tj8h63LNXV_vKBEegn7L2OjEpNOBjY63T-omr2qwMRtKQGwG0ihEa-9ML_Y_MRXHBlvxuIMFsRSR_169Kn2AO-Qx8lcabVTDOwgx-s7CoHnI3XLoYQF64vO2zT06LS1ity9KFzyFGG8nQWShO2h-PYdOQEKEXaGJ8DwBsqEPHSH1YTvtL32s_6TN5GUvR7zmf91oXroJ7K59X9C3AwQd1t3qNKef6G-hKocd89O_LiCUWDnXRwDHCkV8R1onn-JtdZ7PJrsOfCedTPWKCFM-z_0Q2ncNh9-DZBIN8jKeHWrECl3_n5Wu6jBGHRQaSS1OrajkDar.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4iLSO4/y2/l/en_US-j/mmGkYkInWJv.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4iA944/yI/l/en_US-j/bFIe4tuld2E.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4idc84/y7/l/en_US-j/QHB9ZRdvqT_.js
Warning::
External script from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v4ieWN4/ye/l/en_US-j/erAdcD-AHORvOKLZrh_DVnYCPfv43i0iwrruBGGEYFdGhwCEsLVMyJV6uBpr9kvHpcAdF4Q4yS3Q5yLIhLjdtTF59V3TtN2HhP51QCeCZRMWgwI6-NhAsCA5LxvyfVWAYRn5Q5XLynIoHzskHM2TrHr72z775NzKCi2Sch9boWyHYdnzATCB6ghfjDQ.js
Warning::
External link from static.xx.fbcdn.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.xx.fbcdn.net/rsrc.php/v5/yn/l/0,cross/A1QZP0ChGIvg8T_6-Yirbb.css
SRI Coverage 0 / 13 of external resources have integrity hashes
TagDomainIntegrity
<link>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<script>static.xx.fbcdn.net✗ Missing
<link>static.xx.fbcdn.net✗ Missing
D
Permissions-Policy
Action
No header set
FIX
No header set
Warning::
No Permissions-Policy header
Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()
B
WAF / Bot Protection
No WAF detected via response headers
REVIEW
No WAF detected via response headers
Info::
No WAF detected
Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.
B
CSP Inline-Style Readiness
9 inline style attribute(s) detected
REVIEW
9 inline style attribute(s) detected
Info::
9 inline style attribute(s) detected
Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 9 inline style(s) is low. Affected element types include: span, label, i, div. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.
C
Permissions-Policy Granularity
Action
No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin
REVIEW
No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin
Warning::
Permissions-Policy header not set -- features default to allow-on-same-origin
Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need: ``` Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=() ``` Features the page legitimately uses can stay enabled with `feature=(self)`.
Got: header absent
B
Referrer-Policy Strictness
Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)
REVIEW
Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)
Info::
Referrer-Policy header not set -- browser default applies
Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior: ``` Referrer-Policy: strict-origin-when-cross-origin ``` This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.
Got: header absent
B
Open Redirect Surface
1 link(s) carry redirect-shaped query parameter(s)
REVIEW
1 link(s) carry redirect-shaped query parameter(s)
Info::
1 link(s) carry redirect-shaped query parameter(s)
Heuristic flag -- whether each endpoint actually permits an arbitrary redirect target depends on server-side validation. Audit the listed paths' redirect-target handling: the endpoint should either (a) restrict to a relative path, (b) restrict to an allowlisted host set, or (c) sign the target. Open redirects power phishing flows (the attacker's URL begins with your trusted domain) and bypass some SSRF-mitigation cookie scoping. Common parameter names flagged: redirect, redirect_uri, redirect_url, redirecturl, return, returnto, return_to, returnurl, return_url, next, nexturl, next_url, continue, goto, dest, destination, forward, target.
Got: /reg/?entry_point=login&next=?next=...
B
Email Security
DMARC: reject, MTA-STS: testing, TLS-RPT
REVIEW
DMARC: reject, MTA-STS: testing, TLS-RPT
Info::
DMARC policy is reject — strongest protection
Warning::
SPF record has no `all` mechanism
Without a trailing `all` mechanism, receivers fall back to neutral for any sender not explicitly listed -- effectively no enforcement. Append -all (or ~all during rollout).
Info::
No DKIM detected via common selectors
DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
Info::
MTA-STS in testing mode
Testing mode reports failures without enforcing the policy. Promote to enforce after monitoring TLS-RPT reports.
Info::
TLS-RPT configured
Got: mailto:sts-reports@facebookmail.com
Info::
BIMI not configured
BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.
DMARC
Policy reject — strongest protection Record v=DMARC1; p=reject; rua=mailto:a@dmarc.facebookmail.com; ruf=mailto:fb-dmarc@datafeeds.phishlabs.com; pct=100

Without a trailing `all` mechanism, receivers fall back to neutral for any sender not explicitly listed -- effectively no enforcement. Append -all (or ~all during rollout).

Why this matters

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

DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.

Why this matters

No DKIM signature on outbound mail — receivers can't cryptographically prove the message came from your domain.

Learn more ▾

DKIM signs outbound mail with a private key whose public half lives in DNS at <selector>._domainkey.<domain>. Without DKIM, DMARC alone can't tell legitimate mail from spoofs, and large mailbox providers (Gmail, Yahoo) increasingly require DKIM for inbox placement. Note: this check probes a curated list of common selectors; non-standard selectors produce a false negative.

Source: RFC 6376 / Google + Yahoo 2024 sender requirements

Testing mode reports failures without enforcing the policy. Promote to enforce after monitoring TLS-RPT reports.

Why this matters

MTA-STS testing mode reports failures but doesn't enforce — your mail is no more protected than without it.

Learn more ▾

Testing mode is for the rollout phase: senders log TLS failures (via TLS-RPT) but still deliver. Once you've reviewed reports and confirmed no legitimate mail is rejected, promote the policy to mode: enforce.

Source: RFC 8461 §5

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

Why this matters

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

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
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_AES_128_GCM_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
OCSP stapling not enabled
Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
Info::
Certificate is valid (expires in 7 days)
Got: 2026-07-16T23:59:59Z
Warning::
Certificate expires soon (7 days remaining)
Renew the certificate before it expires to avoid browser warnings.
Got: 2026-07-16T23:59:59Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 11 domain(s)
Got: *.facebook.com, *.facebook.net, *.fbcdn.net, *.fbsbx.com, *.m.facebook.com, *.messenger.com, *.xx.fbcdn.net, *.xy.fbcdn.net, *.xz.fbcdn.net, facebook.com, messenger.com
Info::
Certificate is issued by a trusted CA
Got: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US

Renew the certificate before it expires to avoid browser warnings.

Why this matters

Cert expiry within the renewal window — fix now while there's no user impact, instead of after expiry when there's a full outage.

Learn more ▾

Most CAs recommend renewal at 30 days remaining. Inside that window, schedule the renewal immediately and verify auto-renewal is configured if applicable. Don't wait until 7 days; weekend / holiday timing can leave you exposed.

Source: Let's Encrypt / CA renewal best practice

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

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Why this matters

Without OCSP stapling, every first-time visitor pays an extra OCSP roundtrip — and the CA learns who's visiting your site.

Learn more ▾

OCSP stapling has the server fetch its own revocation status from the CA and attach the signed response to the TLS handshake. Without it, browsers contact the CA directly: extra latency for the user and a privacy leak (the CA sees who connected). Enable ssl_stapling on (nginx) / SSLUseStapling On (Apache) / OCSPStapling = on (Caddy auto-enables).

Source: RFC 6961 / Mozilla Server-Side TLS guide

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

Certificate Chain

Leaf Certificate
Subject CN=*.facebook.com,O=Meta Platforms\, Inc.,L=Menlo Park,ST=California,C=USIssuer CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USValid 2026-04-17T00:00:00Z → 2026-07-16T23:59:59ZExpires in 7 days — expiring soon! SANs *.facebook.com, *.facebook.net, *.fbcdn.net, *.fbsbx.com, *.m.facebook.com, *.messenger.com, *.xx.fbcdn.net, *.xy.fbcdn.net, *.xz.fbcdn.net, facebook.com, messenger.comSignature SHA256-RSASerial bb50bab8b8a0e7e19851a2f22a0c907
Intermediate (CA Certificate)
Subject CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2021-03-30T00:00:00Z → 2031-03-29T23:59:59ZExpires in 1724 days Signature SHA256-RSASerial cf5bd062b5602f47ab8502c23ccf066
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+
security.txt
Vulnerability disclosure policy
PASS
Vulnerability disclosure policy
Info::
security.txt found
Got: https://facebook.com/.well-known/security.txt

security.txt

Contact: https://www.facebook.com/whitehat/report/
Expires: 2026-08-08T00:46:58-07:00
A+
Cross-Origin Tab Safety
All 4 new-tab link(s) carry rel=noopener
PASS
All 4 new-tab link(s) carry rel=noopener
Info::
All 4 new-tab link(s) carry rel=noopener
A+
Trusted Types (XSS Sink Hardening)
No CSP header -- Trusted Types check is N/A
PASS
No CSP header -- Trusted Types check is N/A
Info::
No CSP header found -- Trusted Types check is N/A
A+
Bot Challenge Detection
Scan reached real page content (no bot-protection interstitial)
PASS
Scan reached real page content (no bot-protection interstitial)
Info::
No bot-protection interstitial detected -- the rest of the report reflects the real page
A+
Soft-404 Detection
HTTP status is non-2xx -- soft-404 check is N/A
PASS
HTTP status is non-2xx -- soft-404 check is N/A
Info::
HTTP status is non-2xx -- soft-404 check is N/A
A+
Empty Page Detection
Page has substantive body text and no placeholder / template-leak signals
PASS
Page has substantive body text and no placeholder / template-leak signals
Info::
Page has substantive body text and no placeholder / template-leak signals
A+
Geo-Restriction Detection
No geo-restriction signals detected -- scan reached the page from an allowed region
PASS
No geo-restriction signals detected -- scan reached the page from an allowed region
Info::
No geo-restriction detected
A+
Maintenance Mode Detection
No maintenance-mode signals detected -- scan reached a normal page
PASS
No maintenance-mode signals detected -- scan reached a normal page
Info::
No maintenance-mode signals detected
A+
CORS Depth
No CORS response headers -- the resource is same-origin-only by browser default
PASS
No CORS response headers -- the resource is same-origin-only by browser default
Info::
No CORS response headers -- the resource is same-origin-only by browser default
A+
Source Map Exposure
Source-map probe didn't run on this scan
PASS
Source-map probe didn't run on this scan
Info::
Source-map probe didn't run on this scan
A+
HTML Version Disclosure
No software-version disclosures in HTML
PASS
No software-version disclosures in HTML
Info::
No software-version disclosures in HTML
A
Auth Security
2 auth-security finding(s) on the login page
PASS
2 auth-security finding(s) on the login page
Info::
Login page detected
The page contains a `type=password` input and at least one identifier field (username / email). Auth-security findings below evaluate the page's hardening posture.
Warning::
Login form does not contain a recognizable CSRF token
Standard frameworks emit CSRF tokens as a hidden input named `_csrf`, `csrf_token`, `csrfmiddlewaretoken` (Django), `authenticity_token` (Rails), or `__RequestVerificationToken` (ASP.NET). None of those were found. Possibilities: (1) the form posts to an API that uses a custom header or SameSite cookie reliance for CSRF -- legitimate but not visible from this scan, (2) the form is genuinely missing CSRF protection, which would let an attacker submit logins from another origin via a hidden POST. Verify the auth flow has SOME CSRF defense.
A+
Subdomain Inventory Exposure
No risky subdomain names in certificate SANs
PASS
No risky subdomain names in certificate SANs
Info::
No risky subdomain names in certificate SANs
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::
security.txt is present — good practice
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✗ ExposedSecurity PolicyInfo
/package.json✓ Not founddependency-manifest—
/composer.json✓ Not founddependency-manifest—
/Gemfile✓ Not founddependency-manifest—
/Gemfile.lock✓ Not founddependency-manifest—
/requirements.txt✓ Not founddependency-manifest—
/pom.xml✓ Not founddependency-manifest—
/.gitlab-ci.yml✓ Not foundci-config—
/.travis.yml✓ Not foundci-config—
A+
API Surface
No API specs or GraphQL introspection found (probed 11 candidate path(s))
PASS
No API specs or GraphQL introspection found (probed 11 candidate path(s))
Info::
No API specs or GraphQL introspection found (probed 11 path(s))
A
Transport Security
HTTP/3, HSTS, and TLS version analysis
PASS
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) supported
The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
Warning::
HSTS max-age is short: 180 days
HSTS max-age should be at least 1 year (31536000 seconds).
Got: max-age=15552000 (expected 31536000)
Info::
HSTS missing includeSubDomains
Without includeSubDomains, HSTS only protects the exact domain.
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