Open
Cached
·
just now
73/100
SECURITY SCORE
Certificate Information
Subject
CN=naver.co.kr
Issuer
C=US, O=Let's Encrypt, CN=E5
Valid From
August 14, 2025
Valid Until
November 12, 2025
5 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
45:3D:F7:F5:C6:B5:FA:69:B1:53:5A:36:16:80:04:12:6D:DE:7F:1A:2C:E7:85:EB:7D:B3:04:FA:10:01:B0:72
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
Present
max-age=63072000; includeSubdomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Present
unsafe-url
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Content-Type-Options: nosniff
- • 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
Subject Alternative Names
13 domains
naver.com
new.www.naver.com
next.www.naver.com
naver.co.kr
www.naver.co.kr
naver.asia
www.naver.asia
naver.co
www.naver.co
naver.kr
www.naver.kr
naver.net
www.naver.net
Other domains in certificate