Open
Cached
·
just now
82/100
SECURITY SCORE
Certificate Information
Subject
C=JP, ST=Tokyo, L=Shibuya, O=GMO GlobalSign K.K., CN=seal-stg.atlas.globalsign.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign RSA OV SSL CA 2018
Valid From
June 10, 2025
Valid Until
July 12, 2026
248 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
75:4D:E9:95:BC:6D:7A:8E:2D:70:AD:A9:00:30:AA:29:2A:C5:3F:E3:48:D5:EE:5E:F5:78:C2:52:6F:1F:B9:3C
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
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