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 *.clo.footprintdns.com, *.hotmail.com, *.internal.outlook.com, *.live.com, *.nrb.footprintdns.com, *.office.com, *.office365.com, *.outlook.com, *.outlook.office365.com, not for webmail.evolutiontrustees.com.au

Cached · just now
82/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=outlook.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Cloud Services CA-1
Valid From
November 10, 2025
Valid Until
November 09, 2026 280 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
39:35:BF:CC:EC:88:80:E3:C4:5B:DE:DF:90:CF:5D:28:7F:E6:38:0D:1A:BD:72:B6:D3:06:E3:F6:4F:CD:3A:A4
Alternative Names
23 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
Good
max-age=31536000; includeSubDomains
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
  • • Consider adding 'preload' to HSTS for maximum security
  • • 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
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
digicert.com globalsign.com entrust.net microsoft.com
Incident Reporting
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 4 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'issuewild' records to control wildcard certificate issuance