DNS Gurus
Cached · just now
83/100 SECURITY SCORE

Certificate Information

Subject
C=CH, L=Zürich, O=ABB Asea Brown Boveri Ltd, CN=vpn.xe.abb.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
September 02, 2025
Valid Until
September 01, 2026 225 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
FC:C8:79:76:77:08:2C:AA:93:82:A7:48:34:CA:86:DB:12:15:28:14:25:40:22:40:09:49:7E:5F:48:9F:30:FE
Alternative Names
4 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=31536000
Content-Security-Policy
Basic
default-src; frame-ancestors; base-uri; +1 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • 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