Security
· 32 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.FEmpty Page DetectionAction1 empty-page signal(s) detected -- page may be a placeholder or have content-rendering bugsFIX
FSubresource Integrity AdoptionAction0% SRI adoption (0/41 third-party resources)FIX
FPermissions-Policy GranularityAction0% high-risk feature coverage (0/10)FIX
FSubresource IntegrityAction0 of 41 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <link> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
| <script> | r.bing.com | ✗ Missing |
CSecurity HeadersAction5 of 10 headers properly configuredREVIEW
This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
nosniffMIME 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.
DENYWithout 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.
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
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
CContent Security PolicyAction5 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.
frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
frame-ancestors 'self'Security gaps expose your site and users to attacks, eroding trust.
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
BWAF / Bot ProtectionNo WAF detected via response headersREVIEW
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
BSubdomain Inventory Exposure2 risky subdomain name(s) in certificate SANsREVIEW
BEmail SecurityDMARC: reject, SPF: -allREVIEW
The policy file exists but no _mta-sts TXT record was found. Senders rely on the TXT record to discover and version the policy.
MTA-STS policy file is reachable but no _mta-sts TXT record exists, so senders can't discover or version-pin the policy.
Learn more ▾ ▴
Senders look up the _mta-sts TXT record first to learn the current policy ID; without it they treat the policy as absent. Publish a TXT record at _mta-sts.<domain> with v=STSv1; id=<policy-version>.
Source: RFC 8461 §3.1
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.
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
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
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.
Security gaps expose your site and users to attacks, eroding trust.
CPermissions-PolicyAction1 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
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+Cross-Origin Tab SafetyNo new-tab links found -- no tabnabbing surfacePASS
A+CSP Inline-Style ReadinessNo inline style attributes -- strict CSP is feasiblePASS
A+Bot Challenge DetectionScan reached real page content (no bot-protection interstitial)PASS
A+Soft-404 DetectionHTTP status is non-2xx -- soft-404 check is N/APASS
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 1 candidate URL(s))PASS
A+HTML Version DisclosureNo software-version disclosures in HTMLPASS
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+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 | — |