Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=supremeopti.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 05, 2026
Valid Until
July 04, 2026
55 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
43:1A:45:0F:DC:24:48:9A:FC:D1:16:3D:9A:1D:E2:9D:1A:47:4A:49:9F:58:5D:03:35:BE:14:B0:D0:1E:15:42
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
Good
max-age=31536000, max-age=31536000; includeSubDomains, max-age=31536000; includeSubDomains
X-Frame-Options
Present
SAMEORIGIN, SAMEORIGIN, SAMEORIGIN
X-Content-Type-Options
Present
nosniff, nosniff, nosniff
Referrer-Policy
Present
strict-origin-when-cross-origin, strict-origin-when-cross-origin, strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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