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 *.azurewebsites.net, *.scm.azurewebsites.net, *.sso.azurewebsites.net, *.swedencentral-01.azurewebsites.net, *.scm.swedencentral-01.azurewebsites.net, *.sso.swedencentral-01.azurewebsites.net, *.swedencentral.c.azurewebsites.net, *.scm.swedencentral.c.azurewebsites.net, *.sso.swedencentral.c.azurewebsites.net, not for waws-prod-sec-029-83b2.swedencentral.cloudapp.azure.com

Certificate Information

Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=*.azurewebsites.net
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 07
Valid From
October 05, 2025
Valid Until
August 25, 2026 267 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
1C:E5:9F:9F:42:11:13:B6:CD:9E:CC:A7:8E:AE:34:4C:E8:80:90:0E:CA:A8:DF:7C:F7:79:C0:58:23:22:9D:35
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