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

Security

· 32 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
85
GRADE
B
FIX
3
REVIEW
9
PASS
20
INFO
0
Checks
32
20 PASS 9 REVIEW 3 FIX
F
Subresource Integrity Adoption
Action
0% SRI adoption (0/31 third-party resources)
FIX
0% SRI adoption (0/31 third-party resources)
Warning::
SRI adoption: 0/31 third-party resources protected (0%)
Of 31 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.snapchat.com/sc-com/_next/static/chunks/0df1fjit3-eki.css - https://static.snapchat.com/sc-com/_next/static/chunks/3dfd4pnq0ojgd.css - https://static.snapchat.com/sc-com/_next/static/chunks/2o87tp_uj4h_z.css - https://static.snapchat.com/sc-com/_next/static/chunks/2bzknqvyd4p7c.js - https://static.snapchat.com/sc-com/_next/static/chunks/2ixdagnet62bq.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/31)
F
Subresource Integrity
Action
0 of 31 external resources have SRI
FIX
0 of 31 external resources have SRI
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/sc-com/_next/static/chunks/0df1fjit3-eki.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/sc-com/_next/static/chunks/3dfd4pnq0ojgd.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/sc-com/_next/static/chunks/2o87tp_uj4h_z.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/sc-com/_next/static/chunks/2bzknqvyd4p7c.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/sc-com/_next/static/chunks/2ixdagnet62bq.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/sc-com/_next/static/chunks/086z_40o_asn6.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/sc-com/_next/static/chunks/1ibbpcpmwlh0d.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/sc-com/_next/static/chunks/3si3zz30u_3si.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/sc-com/_next/static/chunks/1338q2gqq4_ty.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/sc-com/_next/static/chunks/0_fhbp-k4h863.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/sc-com/_next/static/chunks/3tv5rgbmmlba1.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/sc-com/_next/static/chunks/2y2d3ymlnaajr.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/sc-com/_next/static/chunks/17go2t_jfbskg.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/sc-com/_next/static/chunks/turbopack-32uqd6jq9mqqv.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/sc-com/_next/static/chunks/3-15q-3muzh0k.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/sc-com/_next/static/chunks/31k_al8sw9nbf.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/sc-com/_next/static/chunks/1vrwdx_c2a6u-.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/sc-com/_next/static/chunks/14gbvm3p0jx8d.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/sc-com/_next/static/chunks/1wm2ljmpghcob.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/sc-com/_next/static/chunks/0ccyisuegtzyp.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/sc-com/_next/static/chunks/0xnwlao2hwnp7.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/sc-com/_next/static/chunks/2mzbfu8866ozi.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/sc-com/_next/static/chunks/27y8fdeiog6qg.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/sc-com/_next/static/chunks/4305ig8qrb1s6.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/sc-com/_next/static/chunks/0i_q7oob5f-8m.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/sc-com/_next/static/chunks/1qp6s1znjuemy.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/sc-com/_next/static/chunks/0cz1d0mv5g_q7.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/sc-com/_next/static/chunks/1b_gt8dq-l2x4.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/sc-com/_next/static/chunks/2skb-kvjw6q4l.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/sc-com/_next/static/chunks/0fw8_3fbkx8ux.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/sc-com/_next/static/chunks/07tl871vt3h5b.js
SRI Coverage 0 / 31 of external resources have integrity hashes
TagDomainIntegrity
<link>static.snapchat.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
<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
<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, no SPF
FIX
no DMARC, no SPF
Warning::
No DMARC record found
Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
Warning::
No SPF record found
Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
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 not configured
MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
Info::
TLS-RPT not configured
TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
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

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. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

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

Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.

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

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

Why this matters

Without MTA-STS, inbound mail can be silently downgraded to plain SMTP by a network attacker.

Learn more ▾

MTA-STS (RFC 8461) tells sending mail servers to use TLS and to refuse delivery if TLS fails. Requires both a TXT record at _mta-sts.<domain> AND a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Without it, an active attacker on the network path can strip STARTTLS and read the email in plaintext.

Source: RFC 8461

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

Why this matters

Without TLS-RPT, you have no visibility into inbound TLS failures — MTA-STS misconfigurations stay hidden until users complain.

Learn more ▾

TLS-RPT (RFC 8460) is the feedback channel for MTA-STS: senders post aggregate reports of TLS-handshake failures to the URI in your _smtp._tls TXT record. Without it, an MTA-STS misconfiguration silently rejects mail and you find out only when someone notices missing email.

Source: RFC 8460

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
Security Headers
7 of 10 headers properly configured
REVIEW
7 of 10 headers properly configured
Info::
HSTS is enabled
Got: max-age=31536000; includeSubDomains
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: strict-origin-when-cross-origin
Info::
Permissions-Policy is set
Got: camera=(), microphone=(), geolocation=(), payment=()
Info::
Content-Security-Policy is present
Got: default-src 'self'; script-src 'wasm-unsafe-eval' 'unsafe-inline' 'self' https:/…
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
Info::
Domain is not in the Chrome HSTS preload list (status: unknown)
Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).
Got: unknown

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

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Why this matters

Not in the Chrome preload list — first-time visitors over plain HTTP can be downgraded by a network attacker before HSTS kicks in.

Learn more ▾

The HSTS header only protects users who have already visited the site (TOFU window). Adding your domain to the Chrome preload list closes that gap so HSTS is enforced from the very first connection. Requires a preload-ready header (max-age=31536000+, includeSubDomains, preload) then submission at hstspreload.org. Inclusion ships in the next Chrome release after acceptance.

Source: hstspreload.org

B
Content Security Policy
8 of 10 CSP checks passed
REVIEW
8 of 10 CSP checks passed
Info::
Raw CSP policy
Got: default-src 'self'; script-src 'wasm-unsafe-eval' 'unsafe-inline' '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'; 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 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://gcp.api.snapchat.com https://sc-static-web-assets-prod.s3.amazonaws.com https://storage.googleapis.com; connect-src 'self' blob: https://gcp.api.snapchat.com https://aws.api.snapchat.com https://*.google-analytics.com https://*.analytics.google.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 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://s.sc-cdn.net https://bolt-gcdn.sc-cdn.net https://accounts.google.com https://iap.googleapis.com https://growth-web-dev-tool.mesh.sc-corp.net; font-src 'self' https://snap-design-system.storage.googleapis.com https://ads-interfaces.sc-cdn.net https://static.snapchat.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:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-src https://iframe.arkoselabs.com https://hcaptcha.com https://*.hcaptcha.com https://www.google.com/recaptcha/ https://recaptcha.google.com/recaptcha/; frame-ancestors https://www.snapchat.com; report-uri https://sentry.sc-prod.net/api/194/security/?sentry_key=82f5202149c04b1abc22a9dcb533a663; upgrade-insecure-requests
Info::
default-src directive is set
Got: default-src 'self'
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 'wasm-unsafe-eval' 'unsafe-inline' '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/
Info::
No 'unsafe-eval' in script source
Info::
No wildcard in script source
Info::
object-src is set to 'none'
Got: object-src 'none'
Info::
base-uri is properly restricted
Got: base-uri 'self'
Info::
frame-ancestors directive is set
Got: frame-ancestors https://www.snapchat.com
Info::
form-action directive is set
Got: form-action 'self'
Info::
upgrade-insecure-requests is enabled

'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

Parsed Policy

default-src 'self'
script-src 'wasm-unsafe-eval''unsafe-inline''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'
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.comhttps://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://gcp.api.snapchat.comhttps://sc-static-web-assets-prod.s3.amazonaws.comhttps://storage.googleapis.com
connect-src 'self'blob:https://gcp.api.snapchat.comhttps://aws.api.snapchat.comhttps://*.google-analytics.comhttps://*.analytics.google.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.comwss: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://s.sc-cdn.nethttps://bolt-gcdn.sc-cdn.nethttps://accounts.google.comhttps://iap.googleapis.comhttps://growth-web-dev-tool.mesh.sc-corp.net
font-src 'self'https://snap-design-system.storage.googleapis.comhttps://ads-interfaces.sc-cdn.nethttps://static.snapchat.com
media-src https://bolt-gcdn.sc-cdn.nethttps://static.snapchat.comhttps://s.sc-cdn.nethttps://cf-st.sc-cdn.netblob:
object-src 'none'
base-uri 'self'
form-action 'self'
frame-src https://iframe.arkoselabs.comhttps://hcaptcha.comhttps://*.hcaptcha.comhttps://www.google.com/recaptcha/https://recaptcha.google.com/recaptcha/
frame-ancestors https://www.snapchat.com
report-uri https://sentry.sc-prod.net/api/194/security/?sentry_key=82f5202149c04b1abc22a9dcb533a663
upgrade-insecure-requests
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
1 inline style attribute(s) detected
REVIEW
1 inline style attribute(s) detected
Info::
1 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. 1 inline style(s) is low. Affected element types include: svg. 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.
B
Trusted Types (XSS Sink Hardening)
Trusted Types not enabled
REVIEW
Trusted Types not enabled
Info::
Trusted Types not enabled
Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.
B
Permissions-Policy Granularity
40% high-risk feature coverage (4/10)
REVIEW
40% high-risk feature coverage (4/10)
Info::
Permissions-Policy covers 4/10 high-risk features (40%)
The Permissions-Policy header explicitly declares policies for 4/10 high-risk features. Covered: camera, microphone, geolocation, payment Not declared (default-allow): usb, serial, midi, accelerometer, gyroscope, magnetometer The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.
Got: 40% (4/10)
C
Subdomain Inventory Exposure
Action
3 risky subdomain name(s) in certificate SANs
REVIEW
3 risky subdomain name(s) in certificate SANs
Warning::
3 risky subdomain name(s) advertised in certificate SANs
These names are publicly visible via Certificate Transparency logs (crt.sh, censys.io) -- any attacker can enumerate them in seconds. Operators are often unaware that internal/staging/admin endpoints are inadvertently advertised this way. Mitigation: use a wildcard cert that doesn't enumerate, issue per-environment certs without non-prod SANs on the prod cert, or move internal services to private DNS off the public cert.
Got: sc-gw-dev.snapchat.com, snap-dev.net, snappcm-dev.com
B
Permissions-Policy
4 directives, 1 missing
REVIEW
4 directives, 1 missing
Info::
camera=() — blocked for all origins
Info::
microphone=() — blocked for all origins
Info::
geolocation=() — blocked for all origins
Info::
payment=() — blocked for all origins
Info::
usb not restricted
Consider adding usb=() to block usb access from embedded content.

Raw Header

camera=() microphone=() geolocation=() payment=()

Feature Permissions

Blocked Self Only Unrestricted Not Set
camera Blocked
microphone Blocked
geolocation Blocked
payment Blocked
usb Not Set
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, 8 checks passed
PASS
TLS 1.3, 8 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 negotiated
Got: h2
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 151 days)
Got: 2027-04-11T23: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

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
h2 (HTTP/2)

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-09-25T00:00:00Z → 2027-04-11T23:59:59ZExpires in 151 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 bb988b4091dd18c3bba381715b9d205
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 1599 days Signature SHA256-RSASerial cf5bd062b5602f47ab8502c23ccf066
A
Cookie Security
2 cookies analyzed, 4 checks passed
PASS
2 cookies analyzed, 4 checks passed
Info::
Cookie 'sc-wcid' has the Secure flag
Warning::
Cookie 'sc-wcid' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Info::
Cookie 'sc-wcid' has SameSite=Lax
Info::
Cookie 'sc-config-cache-key' has the Secure flag
Warning::
Cookie 'sc-config-cache-key' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Info::
Cookie 'sc-config-cache-key' has SameSite=Lax
2 cookies analyzed 2 warnings
NameSecureHttpOnlySameSiteSizeIssues
sc-wcid✓✗Lax43 B1
sc-config-cache-key✓✗Lax35 B1
A
security.txt
Vulnerability disclosure policy
PASS
Vulnerability disclosure policy
Info::
security.txt found
Got: https://www.snapchat.com/.well-known/security.txt
Warning::
security.txt: Missing required 'Expires' field (RFC 9116)

security.txt

Contact: https://hackerone.com/snapchat
Policy: https://snapchat.com/.well-known/security.txt
A+
Cross-Origin Tab Safety
All 5 new-tab link(s) carry rel=noopener
PASS
All 5 new-tab link(s) carry rel=noopener
Info::
All 5 new-tab link(s) carry rel=noopener
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
No soft-404 patterns detected in page title or headings
PASS
No soft-404 patterns detected in page title or headings
Info::
No soft-404 patterns detected in page title or headings
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+
Referrer-Policy Strictness
Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)
PASS
Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)
Info::
Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin
The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value.
Got: strict-origin-when-cross-origin
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+
Open Redirect Surface
No redirect-shaped query parameters in DOM links
PASS
No redirect-shaped query parameters in DOM links
Info::
No redirect-shaped query parameters in DOM links
A+
Auth Security
Page is not a login form -- auth-security checks are N/A
PASS
Page is not a login form -- auth-security checks are N/A
Info::
Page does not appear to be a login form
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.
Info::
HSTS enabled (includeSubDomains)
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