SSL Check WHOIS
Dashboard / Security Report

teams.cloud.microsoft

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

teams.cloud.microsoft: SSL/TLS grade A+ (HTTPS Monitor)teams.cloud.microsoftA+
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:1063:27:1::14 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2603:1063:27:2::14 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+ 52.123.128.14 IPv4 WHOIS › A+ 52.123.129.14 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-19 16:03 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
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)
teams.cloud.microsoft301 → https://teams.cloud.microsoft/ → … → https://teams.cloud.microsoft/v2/unsupported-browser → 200 OK302 → https://teams.cloud.microsoft/v2/unsupported-browser → 200 OK
  • http://teams.cloud.microsoft redirects to HTTPS.

DNS Records

As a public resolver answered for teams.cloud.microsoft and its domain cloud.microsoft. Looked up 2026-11-19 16:03 UTC · 2 days ago

TypeRecords
teams.cloud.microsoft
A
AAAA
MX None
SPF None
cloud.microsoft
A
AAAA
NS
ns1-33.azure-dns.com ns2-33.azure-dns.net ns3-33.azure-dns.org ns4-33.azure-dns.info
MX None
SPF
v=spf1 -all

Certificate Identity

Common Nameteams.cloud.microsoft
Alt Names teams.cloud.microsoft
IssuerCN=Microsoft TLS G2 RSA CA OCSP 04, O=Microsoft Corporation, C=US
Validity 2026-10-05 to 2027-04-21 (150 days remaining)
KeyRSA 2048 bits (sha384RSA)
Serial Number43013484C592875B55765DAF720000013484C5
SHA256 Fingerprint e0fcc36db6a6c5448e2f49b614dffa125585fb6bd276f2750334419a8694687f
Pin SHA256gy/dK3F/LzXbXfOs7EvfP1U/gL0wfnHbJJKHqIX4Xno=

Certificate Properties

Type OV Organization Validated
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%2004_Partition00047.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 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=teams.cloud.microsoft, O=Microsoft Corporation, L=Redmond, S=WA, C=US (Issuer: CN=Microsoft TLS G2 RSA CA OCSP 04, O=Microsoft Corporation, C=US)
Intermediate CA
CN=Microsoft TLS G2 RSA CA OCSP 04, 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 teams.cloud.microsoft, first seen 2026-10-16; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
e0fcc36db6a6c544… current Microsoft TLS G2 RSA CA OCSP 042026-10-05 → 2027-04-212026-11-19
83da73cd3c4fb41f… Microsoft TLS G2 RSA CA OCSP 042025-12-08 → 2026-12-032026-10-16

Addresses

AddressCertificateSeen
52.123.128.14 e0fcc36db6a6c544… 2026-11-19
52.123.129.14 e0fcc36db6a6c544… 2026-11-19
52.123.128.14 83da73cd3c4fb41f… 2026-10-16
52.123.129.14 83da73cd3c4fb41f… 2026-10-16

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-19 16:03A+TLS 1.3 e0fcc36db6a6c544… 52.123.128.14, 52.123.129.14
2026-10-16 10:16A+TLS 1.3 83da73cd3c4fb41f… 52.123.128.14, 52.123.129.14

Other hosts seen on the same addresses