Skip to content
https://www.snapchat.com

Security

· 13 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
70
GRADE
C
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Security Headers
Action
3 of 10 headers properly configured
FIX
3 of 10 headers properly configured
Warning::
HSTS is missing includeSubDomains
Without includeSubDomains, subdomains can still be accessed over HTTP.
Got: max-age=31536000 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
Info::
X-Frame-Options is properly configured
Got: 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=()
Info::
Content-Security-Policy is present
Got: connect-src 'self' blob: https://gcp.api.snapchat.com https://aws.api.snapchat.c…
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
Warning::
X-Powered-By header reveals technology stack
This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.
Got: Next.js
Info::
Server header is present without version info
Got: API Gateway

Without includeSubDomains, subdomains can still be accessed over HTTP.

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

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more ▾

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

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

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

This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.

Why this matters

X-Powered-By: PHP/7.4.3 advertises your stack to attackers — disable it.

Learn more ▾

X-Powered-By and similar headers (X-AspNet-Version, X-Runtime) tell attackers which versions to target. Disable in your server/framework config: PHP `expose_php=Off`, ASP.NET `<httpRuntime enableVersionHeader="false">`, Express `app.disable('x-powered-by')`.

Source: OWASP

F
Subresource Integrity
Action
0 of 14 external resources have SRI
FIX
0 of 14 external resources have SRI
Warning::
External script from www.google-analytics.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.google-analytics.com/analytics.js
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-DPDHJB4310
Warning::
External link from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/css/653091ed5f536dac.css
Warning::
External link from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/css/440db435a2548ca1.css
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/polyfills-42372ed130431b0a.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/webpack-da1cb1501e637600.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/framework-41b02394b273386f.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/main-2324219b5dd34d31.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/pages/_app-0ad9e43c5ce9c3d8.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/6018-a929ed8e96168083.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/1540-20a56721f07d4ed0.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/chunks/pages/index-4d8c485f82f083cd.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/OVOexCOz_k92F5c94RZO9/_buildManifest.js
Warning::
External script from static.snapchat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static.snapchat.com/snapchat-dot-com/_next/static/OVOexCOz_k92F5c94RZO9/_ssgManifest.js
SRI Coverage 0 / 14 of external resources have integrity hashes
TagDomainIntegrity
<script>www.google-analytics.com✗ Missing
<script>www.googletagmanager.com✗ Missing
<link>static.snapchat.com✗ Missing
<link>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
<script>static.snapchat.com✗ Missing
F
Email Security
Action
No DMARC
FIX
No DMARC
Warning::
No DMARC record found
Without DMARC, email receivers have no policy for handling authentication failures.
DMARC

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures from your domain.

Without DMARC, email receivers have no policy for handling authentication failures.

Why this matters

Without DMARC, anyone can send phishing emails using your domain name.

Learn more ▾

DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.

Source: DMARC.org / NIST

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
Content Security Policy
5 of 10 CSP checks passed
REVIEW
5 of 10 CSP checks passed
Info::
Raw CSP policy
Got: connect-src 'self' blob: https://gcp.api.snapchat.com https://aws.api.snapchat.com https://*.google-analytics.com https://*.analytics.google.com https://stats.g.doubleclick.net https://*.googletagmanager.com https://www.snapchat.com https://app.snapchat.com https://sentry.sc-prod.net https://us-central1-gcp.api.snapchat.com https://accounts.snapchat.com ws: wss: https://static.snapchat.com https://cdn.contentful.com https://story.snapchat.com https://hcaptcha.com https://*.hcaptcha.com https://www.google.com/recaptcha/ https://session.snapchat.com https://graphql.contentful.com https://cf-st.sc-cdn.net https://app.snapchat.com https://s.sc-cdn.net https://bolt-gcdn.sc-cdn.net https://growth-web-dev-tool.mesh.sc-corp.net https://accounts.google.com https://iap.googleapis.com; img-src 'self' blob: data: https://support-tools.storage.googleapis.com https://www.snapchat.com https://story.snapchat.com https://cf-st.sc-cdn.net https://*.google-analytics.com https://*.googletagmanager.com data: https://www.google.com https://www.google.co.uk https://www.google.com.sa https://www.google.ca https://www.google.fr https://www.google.com.no https://www.google.com.au https://static.snapchat.com https://images.bitmoji.com https://impala-media-production.s3.amazonaws.com https://bolt-gcdn.sc-cdn.net https://lens-storage.storage.googleapis.com https://community-lens.storage.googleapis.com https://lens-preview-storage.storage.googleapis.com https://app.snapchat.com https://sc-static-web-assets-prod.s3.amazonaws.com https://storage.googleapis.com; media-src https://bolt-gcdn.sc-cdn.net https://static.snapchat.com https://s.sc-cdn.net https://cf-st.sc-cdn.net blob:; script-src 'wasm-unsafe-eval' 'self' https://static.snapchat.com https://www.google-analytics.com https://*.googletagmanager.com https://hcaptcha.com https://*.hcaptcha.com https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/; style-src 'self' https://static.snapchat.com https://hcaptcha.com https://*.hcaptcha.com 'unsafe-inline'; default-src 'self'; font-src 'self' https://snap-design-system.storage.googleapis.com https://ads-interfaces.sc-cdn.net https://static.snapchat.com; object-src 'self' *.snapchat.com *.snap.com blob:; frame-ancestors https://localhost:3000 https://www.snapchat.com; frame-src https://iframe.arkoselabs.com https://hcaptcha.com https://*.hcaptcha.com https://www.google.com/recaptcha/ https://recaptcha.google.com/recaptcha/; report-uri ; report-to ; block-all-mixed-content
Info::
default-src directive is set
Got: default-src 'self'
Info::
No 'unsafe-inline' in script source
Info::
No 'unsafe-eval' in script source
Info::
No wildcard in script source
Warning::
object-src allows plugin content
Set object-src to 'none' to prevent Flash/Java plugin exploits.
Got: object-src 'self' *.snapchat.com *.snap.com blob: Expected: object-src 'none'
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'
Info::
frame-ancestors directive is set
Got: frame-ancestors https://localhost:3000 https://www.snapchat.com
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

Set object-src to 'none' to prevent Flash/Java plugin exploits.

Expected: object-src 'none'
Why this matters

object-src open in CSP allows Flash/PDF/plugin embedding — a now-deprecated attack vector that should be explicitly blocked.

Learn more ▾

object-src controls <object>, <embed>, and <applet> elements. Modern sites have no need for plugins; setting `object-src 'none'` blocks an entire class of legacy XSS vectors at zero cost. If your CSP missed it, add the directive.

Source: MDN CSP

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

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

connect-src 'self'blob:https://gcp.api.snapchat.comhttps://aws.api.snapchat.comhttps://*.google-analytics.comhttps://*.analytics.google.comhttps://stats.g.doubleclick.nethttps://*.googletagmanager.comhttps://www.snapchat.comhttps://app.snapchat.comhttps://sentry.sc-prod.nethttps://us-central1-gcp.api.snapchat.comhttps://accounts.snapchat.comws:wss:https://static.snapchat.comhttps://cdn.contentful.comhttps://story.snapchat.comhttps://hcaptcha.comhttps://*.hcaptcha.comhttps://www.google.com/recaptcha/https://session.snapchat.comhttps://graphql.contentful.comhttps://cf-st.sc-cdn.nethttps://app.snapchat.comhttps://s.sc-cdn.nethttps://bolt-gcdn.sc-cdn.nethttps://growth-web-dev-tool.mesh.sc-corp.nethttps://accounts.google.comhttps://iap.googleapis.com
img-src 'self'blob:data:https://support-tools.storage.googleapis.comhttps://www.snapchat.comhttps://story.snapchat.comhttps://cf-st.sc-cdn.nethttps://*.google-analytics.comhttps://*.googletagmanager.comdata:https://www.google.comhttps://www.google.co.ukhttps://www.google.com.sahttps://www.google.cahttps://www.google.frhttps://www.google.com.nohttps://www.google.com.auhttps://static.snapchat.comhttps://images.bitmoji.comhttps://impala-media-production.s3.amazonaws.comhttps://bolt-gcdn.sc-cdn.nethttps://lens-storage.storage.googleapis.comhttps://community-lens.storage.googleapis.comhttps://lens-preview-storage.storage.googleapis.comhttps://app.snapchat.comhttps://sc-static-web-assets-prod.s3.amazonaws.comhttps://storage.googleapis.com
media-src https://bolt-gcdn.sc-cdn.nethttps://static.snapchat.comhttps://s.sc-cdn.nethttps://cf-st.sc-cdn.netblob:
script-src 'wasm-unsafe-eval''self'https://static.snapchat.comhttps://www.google-analytics.comhttps://*.googletagmanager.comhttps://hcaptcha.comhttps://*.hcaptcha.comhttps://www.google.com/recaptcha/https://www.gstatic.com/recaptcha/
style-src 'self'https://static.snapchat.comhttps://hcaptcha.comhttps://*.hcaptcha.com'unsafe-inline'
default-src 'self'
font-src 'self'https://snap-design-system.storage.googleapis.comhttps://ads-interfaces.sc-cdn.nethttps://static.snapchat.com
object-src 'self'*.snapchat.com*.snap.comblob:
frame-ancestors https://localhost:3000https://www.snapchat.com
frame-src https://iframe.arkoselabs.comhttps://hcaptcha.comhttps://*.hcaptcha.comhttps://www.google.com/recaptcha/https://recaptcha.google.com/recaptcha/
report-uri
report-to
block-all-mixed-content
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
1 known vulnerability match(es) against detected tech
REVIEW

Known Vulnerabilities

LibraryVersionSeveritySummaryFixed In
Lodash4.17.21medium### Impact Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the `_.unset` and `_.omit` functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. ### Patches This issue is patched on 4.17.23.4.17.23
C
security.txt
Action
Expired (1970-01-01T00:00:00.000Z) — update Expires field
REVIEW

security.txt

Contact: mailto:reportvuln@snapchat.com
Expires: 1970-01-01T00:00:00.000Z
Policy: https://snapchat.com/.well-known/security.txt
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 192 days)
Got: 2026-10-16T23:59:59Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 37 domain(s)
Got: *.snap.com, *.snapchat.com, *.ats.snapchat.com, *.snapads.com, *.snap-dev.net, *.snappcm.com, *.snappcm-dev.com, *.snapar.com, *.snapkit.com, *.arcadiacreativestudio.com, *.bitmoji.com, *.lensstudio.com, *.pixy.com, *.spectacles.com, *.api.snapchat.com, *.sc-gw-dev.snapchat.com, *.saturn.live, *.specs.com, *.api.specs.com, snap.com, snapchat.com, ats.snapchat.com, snapads.com, snap-dev.net, snappcm.com, snappcm-dev.com, snapar.com, snapkit.com, arcadiacreativestudio.com, bitmoji.com, lensstudio.com, pixy.com, spectacles.com, api.snapchat.com, sc-gw-dev.snapchat.com, saturn.live, specs.com
Info::
Certificate is issued by a trusted CA
Got: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,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=*.snap.com,O=Snap Inc.,L=Santa Monica,ST=California,C=USIssuer CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USValid 2026-04-01T00:00:00Z → 2026-10-16T23:59:59ZExpires in 192 days SANs *.snap.com, *.snapchat.com, *.ats.snapchat.com, *.snapads.com, *.snap-dev.net, *.snappcm.com, *.snappcm-dev.com, *.snapar.com, *.snapkit.com, *.arcadiacreativestudio.com, *.bitmoji.com, *.lensstudio.com, *.pixy.com, *.spectacles.com, *.api.snapchat.com, *.sc-gw-dev.snapchat.com, *.saturn.live, *.specs.com, *.api.specs.com, snap.com, snapchat.com, ats.snapchat.com, snapads.com, snap-dev.net, snappcm.com, snappcm-dev.com, snapar.com, snapkit.com, arcadiacreativestudio.com, bitmoji.com, lensstudio.com, pixy.com, spectacles.com, api.snapchat.com, sc-gw-dev.snapchat.com, saturn.live, specs.comSignature SHA256-RSASerial 429c808b76132fd65231fedd3a58e8b
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 1817 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+
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
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.
Info::
HSTS enabled (base policy)
Info::
HSTS missing includeSubDomains
Without includeSubDomains, HSTS only protects the exact domain.
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