Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=tgbhyd.in
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
September 29, 2025
Valid Until
December 28, 2025
35 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
FA:D2:CA:1F:0B:FE:31:42:8B:4E:43:5D:DD:E8:8A:67:E3:04:75:BD:E4:BF:BF:70:AE:33:4E:B6:8B:37:66:A9
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
Good
default-src; script-src; object-src; +2 more
default-src https: 'unsafe-inline'; script-src https: 'unsafe-inline'; object-src 'none'; style-src https: 'unsafe-inline'; font-src https: data:
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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