DNS Gurus
Open Cached · just now
84/100 SECURITY SCORE

Certificate Information

Subject
C=CH, ST=BE, L=Bern, O=Swisscom (Schweiz) AG, CN=www.swisscom.com
Issuer
C=CH, O=SwissSign AG, CN=SwissSign RSA TLS OV ICA 2022 - 1
Valid From
June 26, 2025
Valid Until
June 26, 2026 216 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D2:A0:A9:E5:5E:E3:C4:73:61:CA:70:F6:E5:6D:8D:EF:62:3D:D3:6B:9C:BD:2A:0A:AF:E0:49:D3:EF:79:41:A4
Alternative Names
6 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=16070400; includeSubDomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin
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-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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