Open
Cached
·
just now
82/100
SECURITY SCORE
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<12, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, UNKNOWN=0110-01-040181, UNKNOWN={:asn1_OPENTYPE, <<19, 2, 74, 80>>}, C=JP, ST=Tokyo, L=Shibuya, UNKNOWN={:asn1_OPENTYPE, <<19, 15, 49, 45, 50, 45, 51, 32, 68, 111, 103, 101, 110, 122, 97, 107, 97>>}, O=GMO GlobalSign K.K., CN=gas.globalsign.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign Extended Validation CA - SHA256 - G3
Valid From
April 08, 2025
Valid Until
May 10, 2026
187 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
57:E7:39:41:07:C3:C0:53:D8:D0:48:BF:41:53:60:52:76:07:EA:04:8C:6D:86:19:EA:68:55:F3:FA:BF:2A:94
Alternative Names
Security Configuration
TLS Protocols
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
Subject Alternative Names
16 domains
api.globalsign.com
api01.globalsign.com
api02.globalsign.com
client.globalsign.com
directsystem.globalsign.com
gas.globalsign.com
gcc.globalsign.com
operation.globalsign.com
system.globalsign.com
systemeu.globalsign.com
systemus.globalsign.com
ctl1.epkipro.globalsign.com
ctl1.hcs.globalsign.com
ctl1.system.globalsign.com
ctl2.hcs.globalsign.com
ctl2.system.globalsign.com