Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=nucleussec.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 17, 2026
Valid Until
April 17, 2026
75 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
B4:21:5C:15:25:0E:0E:D5:39:56:6C:4A:6B:4A:F5:FE:7C:75:3F:FC:53:74:B5:C0:2C:8D:2C:A1:DD:B1:00:0E
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Basic
script-src
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
autoplay=*, camera=(self) , cross-origin-isolated=*, display-capture=(self), document-domain=*, encrypted-media=*, geolocation=*, keyboard-map=*, microphone=(self), payment=(self), sync-xhr=*, fullscreen=*
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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