89/100 SECURITY SCORE

Certificate Information

Subject
CN=pre-bee-developers.getbee.info
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
April 10, 2026
Valid Until
October 24, 2026 195 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
79:8C:A1:55:A5:51:7D:86:04:57:A3:71:20:13:B9:1E:07:2C:28:C7:6E:2A:3D:EC:6A:42:8F:EA:A9:87:8F:34
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=31536000
Content-Security-Policy
Weak
frame-ancestors Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
unsafe-url
Permissions-Policy
Present
geolocation=(), camera=(), microphone=()
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives

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