Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=stephenspinks.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 29, 2025
Valid Until
March 29, 2026
61 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F1:D5:54:A9:40:B1:51:2C:A6:B6:6E:AE:80:01:13:5F:37:F1:6D:DA:89:21:32:C7:CA:10:35:C5:6C:D0:4F:82
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=31556926
Content-Security-Policy
Good
default-src; style-src; img-src; +2 more
default-src 'self'; style-src 'unsafe-inline' 'self' fonts.googleapis.com; img-src 'self' img.youtube.com data:; font-src fonts.gstatic.com; frame-src www.youtube.com
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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