DNS Gurus

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 *.azureedge.net, not for workus-web-dev.afd.azureedge.net

Cached · just now
75/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=*.azureedge.net
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft Azure ECC TLS Issuing CA 07
Valid From
January 08, 2026
Valid Until
July 07, 2026 177 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
1F:EA:F3:88:67:FD:5D:96:36:29:2C:E8:98:EE:96:27:7E:4F:D8:FA:B2:51:94:54:44:C3:DE:17:35:59:0D:08
Alternative Names
1 domains

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
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

1 domain
*.azureedge.net