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:

Hostname Mismatch - certificate is issued for *.blob.core.windows.net, *.blz25prdstr03a.store.core.windows.net, *.blob.storage.azure.net, *.z1.blob.storage.azure.net, *.z2.blob.storage.azure.net, *.z3.blob.storage.azure.net, *.z4.blob.storage.azure.net, *.z5.blob.storage.azure.net, *.z6.blob.storage.azure.net, not for download.tinymce.com

75/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=*.blob.core.windows.net
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 07
Valid From
November 14, 2025
Valid Until
May 13, 2026 142 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
05:81:01:46:FE:84:70:13:BC:16:4F:50:08:AC:7D:2F:A6:34:DA:36:96:90:A8:0C:F0:40:3C:53:8E:FC:95:C0
Alternative Names

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)
Warnings
  • TLS 1.1 is deprecated and should be disabled
  • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Add Strict-Transport-Security header with max-age of at least 1 year
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Add X-Content-Type-Options: nosniff
  • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • Consider adding Permissions-Policy to control browser features

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

53 domains
*.blob.storage.azure.net *.z1.blob.storage.azure.net *.z10.blob.storage.azure.net *.z11.blob.storage.azure.net *.z12.blob.storage.azure.net *.z13.blob.storage.azure.net *.z14.blob.storage.azure.net *.z15.blob.storage.azure.net *.z16.blob.storage.azure.net *.z17.blob.storage.azure.net *.z18.blob.storage.azure.net *.z19.blob.storage.azure.net *.z2.blob.storage.azure.net *.z20.blob.storage.azure.net *.z21.blob.storage.azure.net *.z22.blob.storage.azure.net *.z23.blob.storage.azure.net *.z24.blob.storage.azure.net *.z25.blob.storage.azure.net *.z26.blob.storage.azure.net *.z27.blob.storage.azure.net *.z28.blob.storage.azure.net *.z29.blob.storage.azure.net *.z3.blob.storage.azure.net *.z30.blob.storage.azure.net *.z31.blob.storage.azure.net *.z32.blob.storage.azure.net *.z33.blob.storage.azure.net *.z34.blob.storage.azure.net *.z35.blob.storage.azure.net *.z36.blob.storage.azure.net *.z37.blob.storage.azure.net *.z38.blob.storage.azure.net *.z39.blob.storage.azure.net *.z4.blob.storage.azure.net *.z40.blob.storage.azure.net *.z41.blob.storage.azure.net *.z42.blob.storage.azure.net *.z43.blob.storage.azure.net *.z44.blob.storage.azure.net *.z45.blob.storage.azure.net *.z46.blob.storage.azure.net *.z47.blob.storage.azure.net *.z48.blob.storage.azure.net *.z49.blob.storage.azure.net *.z5.blob.storage.azure.net *.z50.blob.storage.azure.net *.z6.blob.storage.azure.net *.z7.blob.storage.azure.net *.z8.blob.storage.azure.net *.z9.blob.storage.azure.net
*.blob.core.windows.net *.blz25prdstr03a.store.core.windows.net