Cached · just now
93/100 SECURITY SCORE

Certificate Information

Subject
CN=*.shopware.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
October 15, 2025
Valid Until
November 13, 2026 318 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
50:DD:B1:AA:E8:18:27:51:7F:BB:00:4C:A9:72:CA:CE:21:2D:27:E1:0F:06:6D:00:B9:DE:0D:F4:7A:A2:49:28
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
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; base-uri; object-src; +13 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(), camera=(), microphone=(), payment=(), fullscreen=(self "https://www.youtube.com" "https://youtube.com"), accelerometer=(self "https://www.youtube.com" "https://youtube.com"), gyroscope=(self "https://www.youtube.com" "https://youtube.com"), magnetometer=(), usb=()
Recommendations
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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

2 domains