SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Expired Certificate - the server's certificate has expired

Cached · just now
77/100 SECURITY SCORE

Certificate Information

Subject
C=DE, ST=Baden-Württemberg, L=Leinfelden-Echterdingen, O=smart Europe GmbH, CN=*.future.smart.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=GeoTrust TLS RSA CA G1
Valid From
July 30, 2024
Valid Until
April 11, 2025 Expired
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C9:D7:0C:C4:D1:11:96:6E:F6:C7:64:36:04:69:92:E0:EA:FC:15:0C:5F:D3:65:50:AC:2C:D8:92:EB:1C:A6:59
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Basic
base-uri; connect-src; font-src; +12 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
autoplay=(self "https://assets.smart.com" "https://s7.future.smart.com" "https://preview3.assetsadobe.com"), accelerometer=(), bluetooth=(), camera=(), clipboard-read=(), clipboard-write=(), display-capture=(), encrypted-media=(self "https://assets.smart.com" "https://s7.future.smart.com" "https://preview3.assetsadobe.com"), fullscreen=(self "https://assets.smart.com" "https://s7.future.smart.com" "https://preview3.assetsadobe.com"), gamepad=(), geolocation=( self "https://*.smart.com"), gyroscope=(), hid=(), keyboard-map=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(self "https://assets.smart.com" "https://s7.future.smart.com" "https://preview3.assetsadobe.com"), screen-wake-lock=(), serial=(), usb=(), web-share=(self), xr-spatial-tracking=()
Recommendations
  • Consider adding 'preload' to HSTS for maximum security
  • 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