Skip to content
https://hiutdenim.co.uk

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
71
GRADE
C
FIX
5
REVIEW
1
PASS
6
INFO
0
Checks
12
6 PASS 1 REVIEW 5 FIX
D
Security Headers
Action
4 of 10 headers properly configured
FIX
4 of 10 headers properly configured
Warning::
HSTS is missing includeSubDomains
Without includeSubDomains, subdomains can still be accessed over HTTP.
Got: max-age=31536000 Expected: max-age=31536000; includeSubDomains
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Warning::
X-Frame-Options header is missing
This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
Expected: DENY
Warning::
Referrer-Policy header is missing
Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
Expected: strict-origin-when-cross-origin
Warning::
Permissions-Policy header is missing
Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
Expected: geolocation=(), camera=(), microphone=()
Info::
Content-Security-Policy is present
Got: base-uri 'self'; default-src self https://*.google.com https://*.google.com.br h…
Warning::
Cross-Origin-Opener-Policy header is missing
COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
Expected: same-origin
Warning::
Cross-Origin-Embedder-Policy header is missing
COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
Expected: require-corp
Info::
X-Powered-By header is not present
Info::
Server header is present without version info
Got: cloudflare

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains
Why this matters

Without 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

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY
Why this matters

Without 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.

Expected: strict-origin-when-cross-origin
Why this matters

Default 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.

Expected: geolocation=(), camera=(), microphone=()
Why this matters

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'.

Expected: same-origin
Why this matters

COOP 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.

Expected: require-corp
Why this matters

COEP 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

F
Subresource Integrity
Action
0 of 13 external resources have SRI
FIX
0 of 13 external resources have SRI
Warning::
External link from cdn.shopify.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.shopify.com/oxygen-v2/42066/36671/77025/3214919/assets/tailwind-NTR0XLcw.css
Warning::
External link from cdn.shopify.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.shopify.com/oxygen-v2/42066/36671/77025/3214919/assets/app-BKGyChOh.css
Warning::
External script from js.smct.io lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://js.smct.io/t/tag-v6.07.js
Warning::
External script from js.smct.io lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://js.smct.io/e/events-1.6.0.min.js?tv=6.07
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=G-Z6W58KW94D&cx=c&gtm=4e6461
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=AW-17676162793
Warning::
External script from www.dwin1.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.dwin1.com/122140.js
Warning::
External script from smct.co lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://smct.co/tm?t=hiutdenim.co.uk
Warning::
External script from widget.envolvetech.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://widget.envolvetech.com/static/js/app.js
Warning::
External script from lantern.roeyecdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://lantern.roeyecdn.com/lantern_global_122140.min.js
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=G-Z6W58KW94D
Warning::
External script from cdn.shopify.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.shopify.com/shopifycloud/privacy-banner/storefront-banner.js
Warning::
External script from cdn.shopify.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.shopify.com/shopifycloud/perf-kit/shopify-perf-kit-spa.min.js
SRI Coverage 0 / 13 of external resources have integrity hashes
TagDomainIntegrity
<link>cdn.shopify.com✗ Missing
<link>cdn.shopify.com✗ Missing
<script>js.smct.io✗ Missing
<script>js.smct.io✗ Missing
<script>www.googletagmanager.com✗ Missing
<script>www.googletagmanager.com✗ Missing
<script>www.dwin1.com✗ Missing
<script>smct.co✗ Missing
<script>widget.envolvetech.com✗ Missing
<script>lantern.roeyecdn.com✗ Missing
<script>www.googletagmanager.com✗ Missing
<script>cdn.shopify.com✗ Missing
<script>cdn.shopify.com✗ Missing
D
Email Security
Action
DMARC: none
FIX
DMARC: none
Warning::
DMARC policy is none — monitoring only
This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.
DMARC
Policy none — monitoring only, does not block spoofing Record v=DMARC1; p=none

This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.

Why this matters

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

D
Permissions-Policy
Action
No header set
FIX
No header set
Warning::
No Permissions-Policy header
Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()
D
security.txt
Action
No /.well-known/security.txt published
FIX

security.txt

No security.txt found at /.well-known/security.txt

B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
No CORS headers present — secure default
CORS Configuration ✓ Secure

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
Content Security Policy
7 of 10 CSP checks passed
PASS
7 of 10 CSP checks passed
Info::
Raw CSP policy
Got: base-uri 'self'; default-src self https://*.google.com https://*.google.com.br https://www.google.co.uk https://*.google-analytics.com/ https://www.googletagmanager.com https://*.g.doubleclick.net https://www.merchant-center-analytics.goog https://*.vimeo.com https://*.envolvetech.com https://www.dwin1.com https://www.dwin2.com https://*.awin1.com https://*.zenaps.com https://the.sciencebehindecommerce.com https://*.wepowerconnections.com https://smct.co https://*.smct.co https://*.smct.io https://lantern.roeyecdn.com https://lantern.roeye.com https://*.appspot.com https://*.cloudfront.net https://*.amazonaws.com 'self' https://cdn.shopify.com https://shopify.com 'nonce-bc552665802e54fed5b381113e105454'; frame-ancestors 'none'; style-src 'self' 'unsafe-inline' https://cdn.shopify.com; connect-src self https://cdn.shopify.com https://monorail-edge.shopifysvc.com https://*.myshopify.com https://*.google.com.br https://*.google.com https://www.google.co.uk https://*.google-analytics.com/ https://www.googletagmanager.com https://*.g.doubleclick.net https://www.merchant-center-analytics.goog https://*.vimeo.com https://*.envolvetech.com https://www.dwin1.com https://www.dwin2.com https://*.awin1.com https://*.zenaps.com https://the.sciencebehindecommerce.com https://*.wepowerconnections.com https://smct.co https://*.smct.co https://*.smct.io https://lantern.roeyecdn.com https://*.appspot.com https://*.cloudfront.net https://*.amazonaws.com 'self' https://monorail-edge.shopifysvc.com https://hiut.myshopify.com https://hiut.myshopify.com; media-src https://*.google.com.br https://cdn.shopify.com https://hiutdenim.co.uk https://hiut.myshopify.com https://*.vimeo.com https://*.envolvetech.com https://smct.co https://*.smct.co https://*.smct.io https://lantern.roeyecdn.com https://*.appspot.com https://*.cloudfront.net https://*.amazonaws.com; frame-src https://*.google.com.br https://www.youtube.com https://*.vimeo.com https://www.googletagmanager.com https://*.envolvetech.com https://www.dwin1.com https://www.dwin2.com https://*.awin1.com https://*.zenaps.com https://the.sciencebehindecommerce.com https://*.wepowerconnections.com https://smct.co https://*.smct.co https://*.smct.io https://lantern.roeyecdn.com https://*.appspot.com https://*.cloudfront.net https://*.amazonaws.com
Info::
default-src directive is set
Got: default-src self https://*.google.com https://*.google.com.br https://www.google.co.uk https://*.google-analytics.com/ https://www.googletagmanager.com https://*.g.doubleclick.net https://www.merchant-center-analytics.goog https://*.vimeo.com https://*.envolvetech.com https://www.dwin1.com https://www.dwin2.com https://*.awin1.com https://*.zenaps.com https://the.sciencebehindecommerce.com https://*.wepowerconnections.com https://smct.co https://*.smct.co https://*.smct.io https://lantern.roeyecdn.com https://lantern.roeye.com https://*.appspot.com https://*.cloudfront.net https://*.amazonaws.com 'self' https://cdn.shopify.com https://shopify.com 'nonce-bc552665802e54fed5b381113e105454'
Info::
No 'unsafe-inline' in script source
Info::
No 'unsafe-eval' in script source
Info::
No wildcard in script source
Info::
object-src falls back to default-src
Info::
base-uri is properly restricted
Got: base-uri 'self'
Info::
frame-ancestors directive is set
Got: frame-ancestors 'none'
Warning::
form-action directive is missing
form-action restricts where forms can submit data, preventing form hijacking.
Expected: form-action 'self'
Info::
upgrade-insecure-requests is not set
This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.
Expected: upgrade-insecure-requests

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests
Why this matters

Without 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

base-uri 'self'
default-src selfhttps://*.google.comhttps://*.google.com.brhttps://www.google.co.ukhttps://*.google-analytics.com/https://www.googletagmanager.comhttps://*.g.doubleclick.nethttps://www.merchant-center-analytics.googhttps://*.vimeo.comhttps://*.envolvetech.comhttps://www.dwin1.comhttps://www.dwin2.comhttps://*.awin1.comhttps://*.zenaps.comhttps://the.sciencebehindecommerce.comhttps://*.wepowerconnections.comhttps://smct.cohttps://*.smct.cohttps://*.smct.iohttps://lantern.roeyecdn.comhttps://lantern.roeye.comhttps://*.appspot.comhttps://*.cloudfront.nethttps://*.amazonaws.com'self'https://cdn.shopify.comhttps://shopify.com'nonce-bc552665802e54fed5b381113e105454'
frame-ancestors 'none'
style-src 'self''unsafe-inline'https://cdn.shopify.com
connect-src selfhttps://cdn.shopify.comhttps://monorail-edge.shopifysvc.comhttps://*.myshopify.comhttps://*.google.com.brhttps://*.google.comhttps://www.google.co.ukhttps://*.google-analytics.com/https://www.googletagmanager.comhttps://*.g.doubleclick.nethttps://www.merchant-center-analytics.googhttps://*.vimeo.comhttps://*.envolvetech.comhttps://www.dwin1.comhttps://www.dwin2.comhttps://*.awin1.comhttps://*.zenaps.comhttps://the.sciencebehindecommerce.comhttps://*.wepowerconnections.comhttps://smct.cohttps://*.smct.cohttps://*.smct.iohttps://lantern.roeyecdn.comhttps://*.appspot.comhttps://*.cloudfront.nethttps://*.amazonaws.com'self'https://monorail-edge.shopifysvc.comhttps://hiut.myshopify.comhttps://hiut.myshopify.com
media-src https://*.google.com.brhttps://cdn.shopify.comhttps://hiutdenim.co.ukhttps://hiut.myshopify.comhttps://*.vimeo.comhttps://*.envolvetech.comhttps://smct.cohttps://*.smct.cohttps://*.smct.iohttps://lantern.roeyecdn.comhttps://*.appspot.comhttps://*.cloudfront.nethttps://*.amazonaws.com
frame-src https://*.google.com.brhttps://www.youtube.comhttps://*.vimeo.comhttps://www.googletagmanager.comhttps://*.envolvetech.comhttps://www.dwin1.comhttps://www.dwin2.comhttps://*.awin1.comhttps://*.zenaps.comhttps://the.sciencebehindecommerce.comhttps://*.wepowerconnections.comhttps://smct.cohttps://*.smct.cohttps://*.smct.iohttps://lantern.roeyecdn.comhttps://*.appspot.comhttps://*.cloudfront.nethttps://*.amazonaws.com
A+
TLS & Certificates
TLS 1.3, 7 checks passed
PASS
TLS 1.3, 7 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_AES_128_GCM_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 74 days)
Got: 2026-06-21T12:03:04Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: ECDSA-SHA384
Info::
Certificate covers 1 domain(s)
Got: hiutdenim.co.uk
Info::
Certificate is issued by a trusted CA
Got: CN=E8,O=Let's Encrypt,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

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

Connection
Protocol
TLS 1.3
Cipher Suite
TLS_AES_128_GCM_SHA256
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=hiutdenim.co.ukIssuer CN=E8,O=Let's Encrypt,C=USValid 2026-03-23T12:03:05Z → 2026-06-21T12:03:04ZExpires in 74 days SANs hiutdenim.co.ukSignature ECDSA-SHA384Serial 6bff859f6557f6256f95cc40a2a17f7237d
Intermediate (CA Certificate)
Subject CN=E8,O=Let's Encrypt,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2024-03-13T00:00:00Z → 2027-03-12T23:59:59ZExpires in 338 days Signature SHA256-RSASerial 63959363c24e7082715918bfc3d7ed56
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
No security.txt found
Consider adding a security.txt at /.well-known/security.txt.
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✓ Not foundSecurity Policy—
A+
Transport Security
HTTP/3, HSTS, and TLS version analysis
PASS
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) supported
The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
Info::
HSTS enabled (base policy)
Info::
HSTS missing includeSubDomains
Without includeSubDomains, HSTS only protects the exact domain.
Info::
TLS 1.3 in use (fastest handshake, 1-RTT)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback