Security
· 13 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.DSecurity HeadersAction4 of 10 headers properly configuredFIX
CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
default-src 'self'Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
Learn more ▾ ▴
Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies or rewrite the page is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever.
Source: OWASP / MDN
Without includeSubDomains, subdomains can still be accessed over HTTP.
max-age=31536000; includeSubDomainsWithout 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
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
FContent Security PolicyActionNo enforcing CSP policy foundFIX
CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.
default-src 'self'Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
Learn more ▾ ▴
Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever. Start in Report-Only mode, fix violations, then graduate to enforcing.
Source: OWASP / MDN
FSubresource IntegrityAction0 of 42 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <script> | a1.adform.net | ✗ Missing |
| <script> | a1.adform.net | ✗ Missing |
| <script> | a1.adform.net | ✗ Missing |
| <script> | a1.adform.net | ✗ Missing |
| <script> | www.youtube.com | ✗ Missing |
| <script> | a1.adform.net | ✗ Missing |
| <script> | a1.adform.net | ✗ Missing |
| <script> | cdn1.adoberesources.net | ✗ Missing |
| <script> | gateway.foresee.com | ✗ Missing |
| <script> | solutions.invocacdn.com | ✗ Missing |
| <script> | solutions.invocacdn.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.youtube.com | ✗ Missing |
| <script> | tags.srv.stackadapt.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | www.everestjs.net | ✗ Missing |
| <script> | ucm-us.verint-cdn.com | ✗ Missing |
| <script> | ucm-us.verint-cdn.com | ✗ Missing |
| <link> | ucm-us.verint-cdn.com | ✗ Missing |
| <script> | ucm-us.verint-cdn.com | ✗ Missing |
| <script> | ucm-us.verint-cdn.com | ✗ Missing |
| <script> | ucm-us.verint-cdn.com | ✗ Missing |
| <script> | ucm-us.verint-cdn.com | ✗ Missing |
| <script> | ucm-us.verint-cdn.com | ✗ Missing |
| <script> | cform.loyalhealth.com | ✗ Missing |
| <link> | tags.srv.stackadapt.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
| <script> | gateway.foresee.com | ✗ Missing |
| <script> | gateway.foresee.com | ✗ Missing |
| <script> | solutions.invocacdn.com | ✗ Missing |
| <script> | solutions.invocacdn.com | ✗ Missing |
| <script> | guide.loyalhealth.com | ✗ Missing |
| <script> | cdn.evgnet.com | ✗ Missing |
| <script> | siteimproveanalytics.com | ✗ Missing |
| <script> | tags.tiqcdn.com | ✗ Missing |
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
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
CKnown vulnerability matchesAction18 known vulnerability match(es) against detected techREVIEW
Known Vulnerabilities
| Library | Version | Severity | Summary | Fixed In |
|---|---|---|---|---|
| Handlebars | 3.0.1 | high | A prototype pollution vulnerability in handlebars is exploitable if an attacker can control the template | 3.0.7 |
| Handlebars | 3.0.1 | high | Versions of `handlebars` prior to 3.0.8 or 4.5.2 are vulnerable to Arbitrary Code Execution. The package's lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript in the system. It can be used to run arbitrary code in a server processing Handlebars templates or on a victim's browser (effectively serving as Cross-Site Scripting). The following template can be used to demonstrate the vulnerability: ```{{#with "constructor"}} {{#with split as |a|}} {{pop (push "alert('Vulnerable Handlebars JS');")}} {{#with (concat (lookup join (slice 0 1)))}} {{#each (slice 2 3)}} {{#with (apply 0 a)}} {{.}} {{/with}} {{/each}} {{/with}} {{/with}} {{/with}}``` ## Recommendation Upgrade to version 3.0.8, 4.5.2 or later. | 3.0.8 |
| Handlebars | 3.0.1 | high | Handlebars before 3.0.8 and 4.x before 4.5.3 is vulnerable to Arbitrary Code Execution. The lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript. This can be used to run arbitrary code on a server processing Handlebars templates or in a victim's browser (effectively serving as XSS). | 3.0.8 |
| Handlebars | 3.0.1 | high | Prototype pollution | 3.0.8 |
| Handlebars | 3.0.1 | high | Versions of `handlebars` prior to 3.0.8 or 4.5.3 are vulnerable to Arbitrary Code Execution. The package's lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript in the system. It is due to an incomplete fix for a [previous issue](https://www.npmjs.com/advisories/1316). This vulnerability can be used to run arbitrary code in a server processing Handlebars templates or on a victim's browser (effectively serving as Cross-Site Scripting) | 3.0.8 |
| Handlebars | 3.0.1 | high | Disallow calling helperMissing and blockHelperMissing directly | 3.0.8 |
| Handlebars | 3.0.1 | medium | Quoteless attributes in templates can lead to XSS | 4.0.0 |
| Handlebars | 3.0.1 | medium | Denial of service | 4.6.0 |
| Handlebars | 3.0.1 | high | Prototype Pollution in handlebars | 4.7.7 |
| Handlebars | 3.0.1 | high | Remote code execution in handlebars when compiling templates | 4.7.7 |
| Moment.js | 2.17.1 | high | Regular Expression Denial of Service (ReDoS) | 2.19.3 |
| Moment.js | 2.17.1 | high | This vulnerability impacts npm (server) users of moment.js, especially if user provided locale string, eg fr is directly used to switch moment locale. | 2.29.2 |
| jQuery | 1.11.2 | medium | 3rd party CORS request may execute | 1.12.0 |
| jQuery | 1.11.2 | medium | parseHTML() executes scripts in event handlers | 2.2.0 |
| jQuery | 1.11.2 | low | jQuery 1.x and 2.x are End-of-Life and no longer receiving security updates | 2.999.999 |
| jQuery | 1.11.2 | medium | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution | 3.4.0 |
| jQuery | 1.11.2 | medium | passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. | 3.5.0 |
| jQuery | 1.11.2 | medium | Regex in its jQuery.htmlPrefilter sometimes may introduce XSS | 3.5.0 |
A+TLS & CertificatesTLS 1.2, 7 checks passedPASS
TLS 1.3 offers improved performance and security. Consider enabling it.
TLS 1.3 not in use — connection falls back to 1.2 and pays the extra round-trip.
Learn more ▾ ▴
Most clients prefer TLS 1.3 if both sides support it. If your server has TLS 1.3 enabled but it's not being negotiated, check for a downgrade-attack mitigation issue or a misconfigured cipher list. nginx ≥ 1.13.0 and OpenSSL ≥ 1.1.1 support TLS 1.3.
Source: RFC 8446 / Mozilla SSL Config
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 | — |