Open
Cached
·
just now
83/100
SECURITY SCORE
Certificate Information
Subject
CN=onstuimig.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 03, 2025
Valid Until
January 01, 2026
38 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
6E:B3:A7:64:65:8F:85:45:92:75:76:8D:00:C0:93:0C:DD:AD:FE:F0:40:89:A5:B8:7D:CB:EA:F2:2C:B2:14:59
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
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
accelerometer=(self),autoplay=*,camera=(self),cross-origin-isolated=(self),display-capture=(self),document-domain=(self),encrypted-media=(self),fullscreen=*,geolocation=(self),gyroscope=(self),magnetometer=(self),microphone=(self),midi=(self),payment=(self),picture-in-picture=*,publickey-credentials-get=(self),screen-wake-lock=(self),sync-xhr=(self),usb=(self),web-share=(self),xr-spatial-tracking=(self)
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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