Security
· 13 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.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 71 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <script> | s3.eu-west-1.amazonaws.com | ✗ Missing |
| <script> | static-resources.botnot.io | ✗ Missing |
| <script> | storm.spicegems.org | ✗ Missing |
| <script> | widgets.automizely.com | ✗ Missing |
| <script> | sdk.postscript.io | ✗ Missing |
| <script> | cdn.corso.com | ✗ Missing |
| <script> | cdn.richpanel.com | ✗ Missing |
| <script> | chimpstatic.com | ✗ Missing |
| <script> | form-assets.mailchimp.com | ✗ Missing |
| <script> | cdn.shopify.com | ✗ Missing |
| <script> | crossborder-integration.global-e.com | ✗ Missing |
| <script> | widgets.automizely.com | ✗ Missing |
| <script> | easygdpr.b-cdn.net | ✗ Missing |
| <script> | cdn.weglot.com | ✗ Missing |
| <script> | cdn1.stamped.io | ✗ Missing |
| <script> | api.joinclyde.com | ✗ Missing |
| <script> | services.nofraud.com | ✗ Missing |
| <script> | j.northbeam.io | ✗ Missing |
| <script> | scripts.clarity.ms | ✗ Missing |
| <script> | bat.bing.com | ✗ Missing |
| <script> | c.amazon-adsystem.com | ✗ Missing |
| <script> | www.clarity.ms | ✗ Missing |
| <script> | cdn.intelligems.io | ✗ Missing |
| <script> | shop.app | ✗ Missing |
| <script> | d2jjzw81hqbuqv.cloudfront.net | ✗ Missing |
| <script> | d2jjzw81hqbuqv.cloudfront.net | ✗ Missing |
| <script> | unpkg.com | ✗ Missing |
| <script> | cdnjs.cloudflare.com | ✗ Missing |
| <script> | cdn.shopify.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | cdn.shopify.com | ✗ Missing |
| <script> | cdn.shopify.com | ✗ Missing |
| <script> | cdn.shopify.com | ✗ Missing |
| <script> | cdn.weglot.com | ✗ Missing |
| <script> | cdn.accessibly.app | ✗ 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.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static.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> | static.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static-tracking.klaviyo.com | ✗ Missing |
| <script> | static-tracking.klaviyo.com | ✗ Missing |
| <link> | cdn.weglot.com | ✗ Missing |
| <link> | static.klaviyo.com | ✗ Missing |
| <link> | a.klaviyo.com | ✗ Missing |
| <script> | cdnjs.cloudflare.com | ✗ Missing |
| <script> | res4.applovin.com | ✗ Missing |
| <script> | res4.applovin.com | ✗ Missing |
| <link> | static.klaviyo.com | ✗ Missing |
| <script> | bat.bing.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | static.klaviyo.com | ✗ Missing |
| <script> | na-library.klarnaservices.com | ✗ Missing |
| <script> | replocdn.com | ✗ Missing |
| <script> | loox.io | ✗ Missing |
| <link> | cdn.shopify.com | ✗ Missing |
| <script> | unpkg.com | ✗ Missing |
| <script> | c.albss.com | ✗ Missing |
| <script> | j.northbeam.io | ✗ 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
Dsecurity.txtActionNo /.well-known/security.txt publishedFIX
security.txt
No security.txt found at /.well-known/security.txt
CSecurity HeadersAction8 of 10 headers properly configuredREVIEW
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
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 matchesAction16 known vulnerability match(es) against detected techREVIEW
Known Vulnerabilities
| Library | Version | Severity | Summary | Fixed In |
|---|---|---|---|---|
| Handlebars | 1.3.0 | high | A prototype pollution vulnerability in handlebars is exploitable if an attacker can control the template | 3.0.7 |
| Handlebars | 1.3.0 | 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 | 1.3.0 | 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 | 1.3.0 | high | Prototype pollution | 3.0.8 |
| Handlebars | 1.3.0 | 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 | 1.3.0 | high | Disallow calling helperMissing and blockHelperMissing directly | 3.0.8 |
| Handlebars | 1.3.0 | medium | Quoteless attributes in templates can lead to XSS | 4.0.0 |
| Handlebars | 1.3.0 | medium | Denial of service | 4.6.0 |
| Handlebars | 1.3.0 | high | Prototype Pollution in handlebars | 4.7.7 |
| Handlebars | 1.3.0 | high | Remote code execution in handlebars when compiling templates | 4.7.7 |
| jQuery | 2.2.3 | low | jQuery 1.x and 2.x are End-of-Life and no longer receiving security updates | 2.999.999 |
| jQuery | 2.2.3 | medium | 3rd party CORS request may execute | 3.0.0-beta1 |
| jQuery | 2.2.3 | medium | parseHTML() executes scripts in event handlers | 3.0.0 |
| jQuery | 2.2.3 | 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 | 2.2.3 | 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 | 2.2.3 | medium | Regex in its jQuery.htmlPrefilter sometimes may introduce XSS | 3.5.0 |
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 | — |