Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=idigitalpayment.in
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 14, 2025
Valid Until
February 12, 2026
70 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
46:3F:80:1E:3F:C6:BF:9B:28:A0:A1:98:BA:13:11:FF:96:63:F2:3E:89:B5:E5:93:FF:CF:09:09:28:B6:33:9F
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
Missing
Not configured
X-Frame-Options
Present
"DENY"
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
"no-referrer-when-downgrade"
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