Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=staging.mrm-uk.dev
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 22, 2025
Valid Until
March 22, 2026
61 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
95:FD:85:86:6B:E0:93:15:BD:06:A0:F5:E0:71:B8:F9:20:84:83:2E:49:21:31:89:ED:D7:28:36:41:AF:E6:E6
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=10886400; preload
Content-Security-Policy
Basic
upgrade-insecure-requests; media-src; img-src; +4 more
upgrade-insecure-requests; media-src https: data: blob:; img-src https: data: blob:; object-src https:; worker-src https: blob:; connect-src https: blob: wss://*.uksouth01.umbraco.io; default-src https: blob: 'unsafe-inline' 'unsafe-eval'
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports