Open
Cached
·
just now
81/100
SECURITY SCORE
Certificate Information
Subject
CN=jiobit.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 21, 2025
Valid Until
February 19, 2026
29 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
17:61:1F:13:69:87:96:F7:05:93:86:77:C6:B3:CB:47:C2:7E:6A:95:8A:A6:80:EA:37:37:C1:05:20:29:48:2F
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
Weak
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • Add X-Content-Type-Options: nosniff
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
letsencrypt.org
pki.goog
pki.goog
; cansignhttpexchanges=yes
amazon.com
comodoca.com
digicert.com
digicert.com
; cansignhttpexchanges=yes
godaddy.com
Wildcard CAs
.
amazon.com
amazontrust.com
awstrust.com
comodoca.com
digicert.com
; cansignhttpexchanges=yes
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 8 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts