Security
· 32 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.DCross-Origin Tab SafetyAction63 of 65 new-tab link(s) missing rel=noopenerFIX
DCSP Inline-Style ReadinessAction52 inline style attribute(s) detectedFIX
DSubresource Integrity AdoptionAction2% SRI adoption (1/37 third-party resources)FIX
FPermissions-Policy GranularityAction0% high-risk feature coverage (0/10)FIX
DHTML Version DisclosureAction4 software version(s) disclosed in HTMLFIX
DSubresource IntegrityAction1 of 37 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <script> | ct.pinterest.com | ✗ Missing |
| <script> | www.gstatic.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | www.youtube.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | connect.facebook.net | ✗ Missing |
| <script> | connect.facebook.net | ✗ Missing |
| <script> | www.gstatic.com | ✗ Missing |
| <script> | www.google-analytics.com | ✗ Missing |
| <script> | www.clarity.ms | ✗ Missing |
| <script> | www.clarity.ms | ✗ Missing |
| <script> | bat.bing.com | ✗ Missing |
| <script> | www.google-analytics.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.youtube.com | ✗ Missing |
| <script> | js.usemessages.com | ✗ Missing |
| <script> | js.hs-banner.com | ✗ Missing |
| <script> | js.hubspot.com | ✗ Missing |
| <script> | js.hs-analytics.net | ✗ Missing |
| <script> | js.hsadspixel.net | ✗ Missing |
| <script> | js.hscollectedforms.net | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <link> | use.typekit.net | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | static.hotjar.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | bat.bing.com | ✗ Missing |
| <script> | js.hs-scripts.com | ✗ Missing |
| <script> | js.hs-scripts.com | ✗ Missing |
| <script> | js.hsforms.net | ✗ Missing |
| <script> | js.hsforms.net | ✗ Missing |
| <script> | static.cloudflareinsights.com | ✓ Protected |
| <script> | js.zi-scripts.com | ✗ Missing |
BSecurity Headers6 of 10 headers properly configuredREVIEW
The header is present and enforced, so first-visit protection is already in place; a short max-age just means the browser forgets it sooner. Set max-age to at least 31536000 (1 year).
max-age=31536000; includeSubDomainsHSTS is on, but a short max-age means browsers forget the policy sooner than recommended — 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
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
same-originCOOP is set to a less-restrictive value (same-origin-allow-popups or unsafe-none) — partial isolation only.
Learn more ▾ ▴
COOP: same-origin is the strictest level. same-origin-allow-popups allows authenticated popup windows back to your origin. unsafe-none is the legacy default (effectively off). Pick the strictest level your app's popup flows tolerate.
Source: MDN COOP
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).
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
BContent Security Policy2 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.
This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.
upgrade-insecure-requestsWithout 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
Csecurity.txtActionNo security.txt file foundREVIEW
security.txt
No security.txt found at /.well-known/security.txt
BTrusted Types (XSS Sink Hardening)Trusted Types not enabledREVIEW
BReferrer-Policy StrictnessReferrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)REVIEW
BEmail SecurityDMARC: quarantine, SPF: ~all, DKIM, BIMIREVIEW
Receivers PERMERROR-fail SPF evaluation when the include/redirect tree exceeds the RFC 7208 10-lookup cap or contains a pathological structure. This is one of the most common silent SPF failures. Flatten the tree by inlining ip4: / ip6: addresses for senders you control, or use a macro-based ESP solution.
Informational: a labeled value pair from the audit.
Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).
Informational: a labeled value pair from the audit.
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.
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>.
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
CPermissions-PolicyAction6 directives, 5 missingREVIEW
Raw Header
Feature Permissions
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, 8 checks passedPASS
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.
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
Certificate Chain
AWAF / Bot ProtectionCloudflarePASS
A+Bot Challenge DetectionScan reached real page content (no bot-protection interstitial)PASS
A+Soft-404 DetectionNo soft-404 patterns detected in page title or headingsPASS
A+Empty Page DetectionPage has substantive body text and no placeholder / template-leak signalsPASS
A+Geo-Restriction DetectionNo geo-restriction signals detected -- scan reached the page from an allowed regionPASS
A+Maintenance Mode DetectionNo maintenance-mode signals detected -- scan reached a normal pagePASS
A+CORS DepthNo CORS response headers -- the resource is same-origin-only by browser defaultPASS
A+Source Map ExposureNo source maps accessible (probed 10 candidate URL(s))PASS
A+Open Redirect SurfaceNo redirect-shaped query parameters in DOM linksPASS
A+Auth SecurityPage is not a login form -- auth-security checks are N/APASS
A+Subdomain Inventory ExposureNo risky subdomain names in certificate SANsPASS
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 | — |
| /package.json | ✓ Not found | dependency-manifest | — |
| /composer.json | ✓ Not found | dependency-manifest | — |
| /Gemfile | ✓ Not found | dependency-manifest | — |
| /Gemfile.lock | ✓ Not found | dependency-manifest | — |
| /requirements.txt | ✓ Not found | dependency-manifest | — |
| /pom.xml | ✓ Not found | dependency-manifest | — |
| /.gitlab-ci.yml | ✓ Not found | ci-config | — |
| /.travis.yml | ✓ Not found | ci-config | — |