Open
Cached
·
just now
84/100
SECURITY SCORE
Certificate Information
Subject
CN=*.bedzzle.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign GCC R6 AlphaSSL CA 2025
Valid From
August 22, 2025
Valid Until
September 23, 2026
236 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DD:70:55:D0:11:7C:9A:55:25:1E:9B:F7:EA:15:80:3A:D4:5E:06:83:20:90:0D:F2:E2:6C:C6:F4:3B:4D:ED:DF
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
Weak
frame-ancestors
X-Frame-Options
Present
ALLOW-FROM SAMEORIGIN, https://smartapp.bedzzle.com/, https://pms-desk-webapp.bedzzle.com, https://smartapp-staging.bedzzle.com/, https://pms-desk-webapp-staging.bedzzle.com, self
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
camera=*, microphone=*
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Significantly strengthen CSP directives
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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