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 *.events.data.microsoft.com, events.data.microsoft.com, *.pipe.aria.microsoft.com, pipe.skype.com, *.pipe.skype.com, *.mobile.events.data.microsoft.com, mobile.events.data.microsoft.com, *.events.data.msn.com, events.data.msn.com, not for teams-events-data.trafficmanager.net
Open
Cached
·
just now
77/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=*.events.data.microsoft.com
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft TLS G2 RSA CA OCSP 10
Valid From
April 14, 2026
Valid Until
October 11, 2026
179 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
47:E7:22:E1:69:BA:40:23:1B:A4:74:35:F2:9E:32:0B:18:C2:57:3B:E5:70:24:49:F0:06:18:65:EC:33:16:AB
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
Present
max-age=31536000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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
13 domains
events.data.microsoft.com
*.events.data.microsoft.com
mobile.events.data.microsoft.com
*.mobile.events.data.microsoft.com
*.pipe.aria.microsoft.com
vortex.data.microsoft.com
*.vortex.data.microsoft.com
events.data.msn.cn
*.events.data.msn.cn
events.data.msn.com
*.events.data.msn.com
pipe.skype.com
*.pipe.skype.com