Cached · just now
95/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=California, L=San Ramon, O=Sailing Union Capital Holding, CN=*.bieases.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
August 13, 2025
Valid Until
September 13, 2026 258 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
72:53:87:D1:46:D1:37:C3:3D:92:D3:8B:7B:1C:23:E9:78:76:81:58:E6:0D:8F:55:B8:F2:83:A8:DC:CE:0E:F4
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=31536000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; font-src; img-src; +5 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Present
geolocation=(),midi=(),sync-xhr=(),microphone=(self "https://static.sumsub.com" "https://api.sumsub.com"),camera=(self "https://static.sumsub.com" "https://api.sumsub.com"),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()
Recommendations
  • Strengthen CSP by removing 'unsafe-eval'

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