Security
· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.DSubresource IntegrityAction1 of 63 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <script> | cdn.shopify.com | ✗ Missing |
| <script> | crossborder-integration.global-e.com | ✗ Missing |
| <script> | assets.dailykarma.io | ✗ Missing |
| <script> | gdprcdn.b-cdn.net | ✗ Missing |
| <script> | static.rechargecdn.com | ✗ Missing |
| <script> | cdn.attn.tv | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | scripts.clarity.ms | ✗ Missing |
| <script> | www.clarity.ms | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | a.klaviyo.com | ✗ Missing |
| <script> | 90e271ce78bc.cdn4.forter.com | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | static.narrativ.com | ✗ Missing |
| <script> | cdn-4.convertexperiments.com | ✗ Missing |
| <script> | cdn.yottaa.com | ✗ Missing |
| <script> | tag.lexer.io | ✗ Missing |
| <link> | www.rarebeauty.com | ✗ Missing |
| <link> | www.rarebeauty.com | ✗ Missing |
| <script> | shop.app | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | www.rarebeauty.com | ✓ Protected |
| <script> | www.rarebeauty.com | ✗ Missing |
| <link> | www.rarebeauty.com | ✗ Missing |
| <script> | bsvrn.rarebeauty.com | ✗ Missing |
| <script> | config.gorgias.chat | ✗ Missing |
| <script> | content.9gtb.com | ✗ Missing |
| <script> | config.gorgias.help | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | cdn.attn.tv | ✗ Missing |
| <script> | cookie-cdn.cookiepro.com | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | studio-assets.cartfulsolutions.com | ✗ Missing |
| <script> | cdn.attn.tv | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | cdn.attn.tv | ✗ Missing |
| <script> | static-tracking.klaviyo.com | ✗ Missing |
| <script> | static-tracking.klaviyo.com | ✗ Missing |
| <script> | static-tracking.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static-tracking.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | content.verasafe.com | ✗ Missing |
| <link> | content.verasafe.com | ✗ Missing |
| <script> | verasafe.com | ✗ Missing |
| <script> | www.rarebeauty.com | ✗ Missing |
| <script> | na-library.klarnaservices.com | ✗ Missing |
| <script> | unpkg.com | ✗ Missing |
| <script> | cookie-cdn.cookiepro.com | ✗ Missing |
| <link> | x.klarnacdn.net | ✗ Missing |
| <script> | static.shopmy.us | ✗ Missing |
| <script> | studio-assets.cartfulsolutions.com | ✗ Missing |
| <script> | config.gorgias.chat | ✗ Missing |
| <script> | cdn.9gtb.com | ✗ Missing |
| <script> | cdn.attn.tv | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
DEmail SecurityActionDMARC: noneFIX
This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.
DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.
Learn more ▾ ▴
DMARC's three policies are p=none (monitor only), p=quarantine (mark as spam), and p=reject (bounce). Most domains start at p=none to gather data, but stay there forever, leaving spoofers unblocked. After 30 days of clean DMARC reports, graduate to p=quarantine, then p=reject.
Source: DMARC.org / NIST
DPermissions-PolicyActionNo header setFIX
No Permissions-Policy header set.
Without this header, embedded iframes can request access to sensitive device features.
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()
Dsecurity.txtActionNo /.well-known/security.txt publishedFIX
security.txt
No security.txt found at /.well-known/security.txt
CSecurity HeadersAction5 of 10 headers properly configuredREVIEW
A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).
max-age=31536000; includeSubDomainsShort 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
Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
strict-origin-when-cross-originDefault 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.
geolocation=(), camera=(), microphone=()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'.
same-originCOOP 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.
require-corpCOEP 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
BContent Security Policy3 of 10 CSP checks passedREVIEW
default-src provides a fallback for other directives. Set it to restrict default resource loading.
default-src 'self'Security gaps expose your site and users to attacks, eroding trust.
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
base-uri 'self'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.
form-action 'self'Security gaps expose your site and users to attacks, eroding trust.
Parsed Policy
BCORS ConfigurationNo CORS headersREVIEW
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 & CertificatesTLS 1.3, 7 checks passedPASS
HTTP/2 provides multiplexing and header compression for better performance.
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
Certificate Chain
A+JS Library VulnerabilitiesNo known vulnerabilitiesPASS
No known JavaScript library vulnerabilities detected.
A+Information LeakageNo exposuresPASS
No sensitive files exposed — all paths returned 404.
| Path | Status | Category | Risk |
|---|---|---|---|
| /.git/HEAD | ✓ Not found | Version Control | — |
| /.git/config | ✓ Not found | Version Control | — |
| /.svn/entries | ✓ Not found | Version Control | — |
| /.env | ✓ Not found | Configuration | — |
| /.env.local | ✓ Not found | Configuration | — |
| /.env.production | ✓ Not found | Configuration | — |
| /wp-config.php | ✓ Not found | Configuration | — |
| /.htaccess | ✓ Not found | Configuration | — |
| /phpinfo.php | ✓ Not found | Debug | — |
| /server-status | ✓ Not found | Debug | — |
| /server-info | ✓ Not found | Debug | — |
| /.well-known/security.txt | ✓ Not found | Security Policy | — |