Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=oceanbuilders.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 30, 2025
Valid Until
February 28, 2026
40 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
CA:5F:4C:E5:1F:D7:71:FC:91:4A:AA:D6:A3:AD:62:22:05:97:08:8D:D8:31:8E:ED:FD:A5:F5:FB:C8:01:41:DE
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=31536000
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(self),autoplay=(self),camera=(self),display-capture=(self),fullscreen=(self),gamepad=(self),geolocation=(self),gyroscope=(self),magnetometer=(self),microphone=(self),usb=(self),xr-spatial-tracking=(self)
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
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