Cached · just now
84/100 SECURITY SCORE

Certificate Information

Subject
C=RU, ST=Moscow, L=Moscow, O=VK LLC, CN=*.vk.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign ECC OV SSL CA 2018
Valid From
January 30, 2026
Valid Until
March 03, 2027 372 days
Public Key
ECDSA 384 bit (P-384) Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
4C:28:49:A6:F1:E1:02:92:0C:39:0F:F4:1F:AB:0A:41:3B:CA:14:12:E6:A0:F3:7A:03:03:04:ED:13:D8:76:DC
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
Present
max-age=15768000
Content-Security-Policy
Basic
default-src; script-src; style-src Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
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