Cached · just now
84/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=California, L=Sunnyvale, O=LinkedIn Corporation, CN=ads.linkedin.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA
Valid From
January 22, 2026
Valid Until
July 22, 2026 151 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
39:81:5C:15:70:45:5B:8C:A9:0D:61:37:86:D7:11:76:C6:0D:EE:FE:4C:C8:42:B0:D2:A4:1A:DD:D9:CB:02:21
Alternative Names

Security Configuration

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

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Basic
base-uri; script-src; worker-src; +9 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Add Strict-Transport-Security header with max-age of at least 1 year
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • 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

Subject Alternative Names

47 domains
ads.linkedin.com dc-dev.ads.linkedin.com dc.ads.linkedin.com dmp-api-dev.ads.linkedin.com dmp-api.ads.linkedin.com email.ads.linkedin.com imp2-dev.ads.linkedin.com imp2.ads.linkedin.com itag.ads.linkedin.com profile-api-dev.ads.linkedin.com profile-api.ads.linkedin.com ap-southeast-1.dc-dev.ads.linkedin.com ap-southeast-1.dc.ads.linkedin.com ap-southeast-1.dmp-api-dev.ads.linkedin.com ap-southeast-1.dmp-api.ads.linkedin.com ap-southeast-1.email.ads.linkedin.com ap-southeast-1.imp2-dev.ads.linkedin.com ap-southeast-1.imp2.ads.linkedin.com ap-southeast-1.profile-api-dev.ads.linkedin.com ap-southeast-1.profile-api.ads.linkedin.com eu-west-1.dc-dev.ads.linkedin.com eu-west-1.dc.ads.linkedin.com eu-west-1.dmp-api-dev.ads.linkedin.com eu-west-1.dmp-api.ads.linkedin.com eu-west-1.email.ads.linkedin.com eu-west-1.imp2-dev.ads.linkedin.com eu-west-1.imp2.ads.linkedin.com eu-west-1.profile-api-dev.ads.linkedin.com eu-west-1.profile-api.ads.linkedin.com us-east-1.dc-dev.ads.linkedin.com us-east-1.dc.ads.linkedin.com us-east-1.dmp-api-dev.ads.linkedin.com us-east-1.dmp-api.ads.linkedin.com us-east-1.email.ads.linkedin.com us-east-1.imp2-dev.ads.linkedin.com us-east-1.imp2.ads.linkedin.com us-east-1.profile-api-dev.ads.linkedin.com us-east-1.profile-api.ads.linkedin.com us-west-2.dc-dev.ads.linkedin.com us-west-2.dc.ads.linkedin.com us-west-2.dmp-api-dev.ads.linkedin.com us-west-2.dmp-api.ads.linkedin.com us-west-2.email.ads.linkedin.com us-west-2.imp2-dev.ads.linkedin.com us-west-2.imp2.ads.linkedin.com us-west-2.profile-api-dev.ads.linkedin.com us-west-2.profile-api.ads.linkedin.com