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 ssl.roles.botframework.com, botframework.com, *.botplinks.botframework.com, *.tokenplinks.botframework.com, *.privatelink.directline.botframework.com, *.privatelink.token.botframework.com, *.botframework.com, *.actions.botframework.com, *.api.botframework.com, not for bc-st.trafficmanager.net
Open
Cached
·
just now
73/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=ssl.roles.botframework.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA
Valid From
November 26, 2025
Valid Until
May 25, 2026
175 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B0:08:5F:C8:B0:7C:D2:8F:B0:78:BD:EB:BD:4C:5C:ED:9D:62:B9:74:BF:99:07:D8:EA:98:89:65:08:51:D0:D2
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
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
28 domains
*.actions.botframework.com
*.alexa.botframework.com
*.api.botframework.com
*.arm.botframework.com
botframework.com
*.botframework.com
*.botplinks.botframework.com
*.dev.botframework.com
*.directline.botframework.com
*.email.botframework.com
*.facebook.botframework.com
*.google.botframework.com
*.groupme.botframework.com
*.kik.botframework.com
*.line.botframework.com
*.privatelink.directline.botframework.com
*.privatelink.token.botframework.com
*.proxy.botframework.com
*.slack.botframework.com
*.sms.botframework.com
ssl.roles.botframework.com
*.telegram.botframework.com
*.testbot.botframework.com
*.token.botframework.com
*.tokenplinks.botframework.com
*.webchat.botframework.com
*.webjobs.botframework.com
*.whatsapp.botframework.com