DNS Gurus
Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=California, L=Sunnyvale, O=LinkedIn Corporation, CN=www.linkedin.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA
Valid From
August 29, 2025
Valid Until
February 28, 2026 30 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
23:0B:A1:13:20:C8:A6:92:57:27:49:55:C4:F7:4C:27:FF:B2:81:1A:55:6C:BF:62:76:E2:7C:A7:49:A9:9D:2B
Alternative Names
39 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
Good
default-src; connect-src; script-src; +9 more
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Strengthen CSP by removing 'unsafe-eval'
  • • 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
Configured (Restricts certificate issuance)
Current Issuer
Not Authorized (Potential misconfiguration)
CAA Issues
  • • CRITICAL: Current certificate issuer 'C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA' is NOT authorized by CAA records. Authorized CAs:
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts