Security
· 13 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.FSecurity HeadersAction2 of 10 headers properly configuredFIX
Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
max-age=31536000; includeSubDomainsWithout HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
Learn more ▾ ▴
HSTS tells browsers 'never speak HTTP to this domain again.' Without it, a network attacker (public WiFi, malicious ISP, hostile DNS) intercepts the first HTTP attempt and serves a downgraded version of your site. One header, big surface reduction.
Source: RFC 6797 / OWASP
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
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
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 30 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <link> | fonts.googleapis.com | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <link> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | www.youtube.com | ✗ Missing |
| <script> | connect.facebook.net | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | connect.facebook.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | www.youtube.com | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ Missing |
| <script> | d16o2fplq2wi4c.cloudfront.net | ✗ 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 matchesAction28 known vulnerability match(es) against detected techREVIEW
Known Vulnerabilities
| Library | Version | Severity | Summary | Fixed In |
|---|---|---|---|---|
| AngularJS | 1.5.9 | medium | Cross-Site Scripting via JSONP | 1.6.0 |
| AngularJS | 1.5.9 | medium | DOS in $sanitize | 1.6.3 |
| AngularJS | 1.5.9 | medium | Universal CSP bypass via add-on in Firefox | 1.6.3 |
| AngularJS | 1.5.9 | low | XSS in $sanitize in Safari/Firefox | 1.6.5 |
| AngularJS | 1.5.9 | low | XSS through SVG if enableSvg is set | 1.6.9 |
| AngularJS | 1.5.9 | high | Prototype pollution | 1.7.9 |
| AngularJS | 1.5.9 | medium | XSS via JQLite DOM manipulation functions in AngularJS | 1.8.0 |
| AngularJS | 1.5.9 | medium | XSS may be triggered in AngularJS applications that sanitize user-controlled HTML snippets before passing them to JQLite methods like JQLite.prepend, JQLite.after, JQLite.append, JQLite.replaceWith, JQLite.append, new JQLite and angular.element. | 1.8.0 |
| AngularJS | 1.5.9 | medium | angular vulnerable to regular expression denial of service via the $resource service | 1.8.4 |
| AngularJS | 1.5.9 | medium | angular vulnerable to regular expression denial of service via the angular.copy() utility | 1.8.4 |
| AngularJS | 1.5.9 | medium | Angular (deprecated package) Cross-site Scripting | 1.8.4 |
| AngularJS | 1.5.9 | medium | angular vulnerable to regular expression denial of service via the <input type="url"> element | 1.8.4 |
| AngularJS | 1.5.9 | low | AngularJS improperly sanitizes SVG elements | 1.8.4 |
| AngularJS | 1.5.9 | low | AngularJS allows attackers to bypass common image source restrictions | 1.8.4 |
| AngularJS | 1.5.9 | high | angular vulnerable to super-linear runtime due to backtracking | 1.8.4 |
| AngularJS | 1.5.9 | low | AngularJS allows attackers to bypass common image source restrictions | 1.8.4 |
| AngularJS | 1.5.9 | medium | AngularJS Incomplete Filtering of Special Elements vulnerability | 1.8.4 |
| AngularJS | 1.5.9 | medium | AngularJS Incomplete Filtering of Special Elements vulnerability | 1.9.8 |
| AngularJS | 1.5.9 | medium | AngularJS Regular expression Denial of Service (ReDoS) | 1.9.9 |
| AngularJS | 1.5.9 | low | End-of-Life: Long term support for AngularJS has been discontinued as of December 31, 2021 | 1.999 |
| Underscore.js | 1.8.3 | high | vulnerable to Arbitrary Code Injection via the template function | 1.12.1 |
| Underscore.js | 1.8.3 | high | ### Impact In simple words, some programs that use `_.flatten` or `_.isEqual` could be made to crash. Someone who wants to do harm may be able to do this on purpose. This can only be done if the program has special properties. It only works in Underscore versions up to 1.13.7. A more detailed explanation follows. In affected versions of Underscore, the `_.flatten` and `_.isEqual` functions use recursion without a depth limit. Under very specific conditions, detailed below, an attacker could exploit this in a Denial of Service (DoS) attack by triggering a stack overflow. A proof of concept (PoC) for this type of attack with `_.isEqual`: ```js const _ = require('underscore'); // build JSON string for nested object ~4500 levels deep // (for this to be an attack, the JSON would have to come from // a request or other untrusted input) let json = ''; for (let i = 0; i < 4500; i++) json += '{"n":'; json += '"x"'; for (let i = 0; i < 4500; i++) json += '}'; // construct two distinct objects with equal shape from the above JSON const a = JSON.parse(json); const b = JSON.parse(json); _.isEqual(a, b); // RangeError: Maximum call stack size exceeded ``` A proof of concept (PoC) for this type of attack with `_.flatten`: ```js const _ = require('underscore'); // build nested array ~4500 levels deep // (like with _.isEqual, this nested array would have to be sourced // from an untrusted external source for it to be an attack) let nested = []; for (let i = 0; i < 4500; i++) nested = [nested]; _.flatten(nested); // RangeError: Maximum call stack size exceeded ``` An application that crashes because of this can be restarted, so the bug is most relevant to applications for which continued operation is important, such as server applications. Furthermore, an application is only vulnerable to this type of attack if ALL of the following conditions are met: - Untrusted input must be used to create a recursive datastructure, for example using `JSON.parse`, with no enforced depth limit. - The datastructure thus created must be passed to `_.flatten` or `_.isEqual`. - In the case of `_.flatten`, the vulnerability can only be exploited if it is possible for a remote client to prepare a datastructure that consists of arrays at all levels AND if no finite depth limit is passed as the second argument to `_.flatten`. - In the case of `_.isEqual`, the vulnerability can only be exploited if there exists a code path in which two distinct datastructures that were submitted by the same remote client are compared using `_.isEqual`. For example, if a client submits data that are stored in a database, and the same client can later submit another datastructure that is then compared to the data that were saved in the database previously, OR if a client submits a single request, but its data are parsed twice, creating two non-identical but equivalent datastructures that are then compared. - Exceptions originating from the call to `_.flatten` or `_.isEqual`, as a result of a stack overflow, are not being caught. All versions of Underscore up to and including 1.13.7 are affected by this weakness. ### Patches The problem has been patched in version 1.13.8. Upgrading to 1.13.8 or later completely prevents exploitation. **Note:** historically, there have been breaking changes in minor releases of Underscore, especially between versions 1.6 and 1.9. However, upgrading from version 1.9 or later to any later 1.x version should be feasible with little or no effort for all users. ### Workarounds A workaround that works for both functions is to enforce a depth limit on the datastructure that is created from untrusted input. A limit of 1000 levels should prevent attacks from being successful on most systems. In systems with highly constrained hardware, we recommend lower limits, for example 100 levels. Another possible workaround that only works for `_.flatten`, is to pass a second argument that limits the flattening depth to 1000 or less. ### References - https://github.com/jashkenas/underscore/issues/3011 - https://underscorejs.org/#1.13.8 - https://underscorejs.org/#flatten - https://underscorejs.org/#isEqual | 1.13.8 |
| jQuery | 1.12.4 | medium | parseHTML() executes scripts in event handlers | 2.2.0 |
| jQuery | 1.12.4 | low | jQuery 1.x and 2.x are End-of-Life and no longer receiving security updates | 2.999.999 |
| jQuery | 1.12.4 | medium | 3rd party CORS request may execute | 3.0.0-beta1 |
| jQuery | 1.12.4 | 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.12.4 | 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.12.4 | medium | Regex in its jQuery.htmlPrefilter sometimes may introduce XSS | 3.5.0 |
BTransport SecurityHTTP/3, HSTS, and TLS version analysisREVIEW
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 | — |