SSL Check WHOIS
Dashboard / Security Report

engage.cloud.microsoft

Overall grade based on: IPv4: 2 of 2 complete · IPv6: 0 of 2 complete, 2 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2603:1061:10:1::13 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2603:1061:10::13 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).

The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.

All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 150.171.73.13 IPv4 WHOIS › A+ 150.171.74.13 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-10-29 07:10 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups secp521r1 secp384r1 secp256r1 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling Yes
HSTS Yes 1 year · includeSubDomains
HSTS Preloading Preloaded
Security Checks
BEAST attack Mitigated
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) No
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_DHE_RSA_WITH_AES_256_GCM_SHA3840x009FDHEFS256Secure
TLS_DHE_RSA_WITH_AES_128_GCM_SHA2560x009EDHEFS128Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.0.4--No
Android 4.1.1--No
Baidu Jan 2015--No
Java 6--No

* Simulated based on server's supported protocols and cipher configuration.

Site Access: HTTP and HTTPS

What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.

Hosthttp:// (port 80)https:// (port 443)
engage.cloud.microsoft301 → https://engage.cloud.microsoft/ → 200 OK200 OK
  • http://engage.cloud.microsoft redirects to HTTPS.

Certificate Identity

Common Nameengage.cloud.microsoft
Alt Names www.yammer.com *.staging.yammer.com *.rt.staging.yammer.com *.staging.assets-yammer.com *.yammerusercontent.com *.rt.yammer.com *.docs.yammer.com *.assets-yammer.com *.yammer.com *.integration.staging.yammer.com *.integration.assets-yammer.com *.yamalytics.yammer.com yammer.com *.eu-1.yammer.com *.engage.cloud-dev.microsoft engage.cloud-dev.microsoft df.engage.cloud.microsoft engage.cloud.microsoft *.test.cosmic.yammer.com *.gov.yammer.com *.rt.gov.yammer.com *.rt.test.cosmic.yammer.com *.engage.cloud.microsoft *.rt.msit.cosmic.yammer.com *.msit.cosmic.yammer.com *.eu.yammer.com *.us.yammer.com *.staging.yammerusercontent.com *.azure-rt.staging.yammer.com yammerusercontent.com *.rt-tx.gov.yammer.com *.us-1.staging.yammer.com *.us-1.yammer.com *.eu-1.assets-yammer.com *.rt.engage.cloud.microsoft *.engage.cloud.dev.microsoft *.rt.engage.cloud.dev.microsoft *.engage.static.dev.microsoft *.engage.static.microsoft
IssuerCN=Microsoft TLS G2 RSA CA OCSP 10, O=Microsoft Corporation, C=US
Validity 2026-10-14 to 2027-01-22 (66 days remaining)
KeyRSA 2048 bits (sha384RSA)
Serial Number490137E2F8D4140A75AA17A35D00000137E2F8
SHA256 Fingerprint 8fb03232892953286c1b2fb1b1d89a428b5d8c16a4d6b571c830b60a19c3fa49
Pin SHA256bBkQ5cGQNpCt6R6bwKlviozeexZ8RQzm/a9MGTNgx14=

Certificate Properties

Type OV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://oneocsp.microsoft.com/ocsp CRL: http://www.microsoft.com/pkiops/crl/partition/Microsoft%20TLS%20G2%20RSA%20CA%20OCSP%2010_Partition00085.crl
DNS CAA Yes (configured) 0 iodef "mailto:[email protected]" 0 issue "digicert.com" 0 issue "microsoft.com" 0 contactemail "[email protected]"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 100 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=*.yammer.com, O=Microsoft Corporation, L=Redmond, S=WA, C=US (Issuer: CN=Microsoft TLS G2 RSA CA OCSP 10, O=Microsoft Corporation, C=US)
Intermediate CA
CN=Microsoft TLS G2 RSA CA OCSP 10, O=Microsoft Corporation, C=US (Issuer: CN=Microsoft TLS RSA Root G2, O=Microsoft Corporation, C=US)
Intermediate CA
CN=Microsoft TLS RSA Root G2, O=Microsoft Corporation, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)

TLS History & Relations

Everything our scans have seen for engage.cloud.microsoft, first seen 2026-06-09; current certificate since 2026-10-29.

Certificates served

Certificate (SHA-256)IssuerValidServed
8fb0323289295328… current Microsoft TLS G2 RSA CA OCSP 102026-10-14 → 2027-01-222026-10-29

Addresses

AddressCertificateSeen
150.171.73.13 8fb0323289295328… 2026-10-29
150.171.74.13 8fb0323289295328… 2026-10-29

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-29 07:10A+TLS 1.3 8fb0323289295328… 150.171.73.13, 150.171.74.13

Other domains on the same certificate

Other hosts seen on the same addresses