Open
Cached
·
just now
81/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 85, 83>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 8, 68, 101, 108, 97, 119, 97, 114, 101>>}, 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=802339, C=US, ST=California, L=Foster City, O=Visa International Service Association, CN=community.developer.cybersource.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2
Valid From
September 15, 2025
Valid Until
September 14, 2026
104 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
FD:4E:9B:E6:3E:53:0C:B5:22:83:F7:4B:9E:55:BE:B3:11:5E:C9:CD:F7:E8:EB:D8:D8:0E:6B:CB:48:3E:14:13
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
Subject Alternative Names
8 domains
community.developer.authorize.net
community.developer.cas.authorize.net
www.community.developer.authorize.net
www.community.developer.cas.authorize.net
community.developer.cas.cybersource.com
community.developer.cybersource.com
www.community.developer.cas.cybersource.com
www.community.developer.cybersource.com