Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=aegisaccounting.co.uk
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 18, 2025
Valid Until
January 16, 2026
41 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
5D:34:CA:75:6F:CA:77:F2:78:4B:7C:5A:EB:D6:40:CA:A1:FD:FD:B4:90:03:6A:CB:DF:AA:D9:6E:DF:88:3B:50
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=15552000; includeSubDomains
Content-Security-Policy
Good
base-uri; block-all-mixed-content; child-src; +17 more
base-uri 'self';block-all-mixed-content;child-src 'none';connect-src 'self' https://app.aegisaccounting.co.uk https://dialogflow.cloud.google.com;default-src 'none';font-src data:;form-action 'none';frame-ancestors https://app.nimble.com;frame-src 'none';img-src data: https://app.aegisaccounting.co.uk;manifest-src https://app.aegisaccounting.co.uk;media-src 'none';object-src 'none';prefetch-src 'none';report-uri https://aegisaccounting.report-uri.com/r/d/csp/enforce;script-src 'unsafe-inline' https://app.aegisaccounting.co.uk https://www.gstatic.com https://static.dialogflow.com;script-src-attr 'unsafe-inline' https://app.aegisaccounting.co.uk https://www.gstatic.com https://static.dialogflow.com;style-src 'unsafe-inline' https://app.aegisaccounting.co.uk;upgrade-insecure-requests;worker-src https://app.aegisaccounting.co.uk
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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