SSL Check WHOIS
Dashboard / Security Report

windows.microsoft.com

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.

windows.microsoft.com: SSL/TLS grade C (HTTPS Monitor)windows.microsoft.comC
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
C

Improvement Required

Overall Rating
2.18.143.160 · WHOIS ›
Assessed 2026-11-22 14:40 UTC

Grade Breakdown

Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at C: server accepts RC4 cipher suites.

Security Vulnerabilities Detected

  • •Obsolete TLS versions (1.0/1.1) supported.
  • •Insecure RC4 cipher supported.
  • •Weak 3DES cipher supported (Sweet32).
  • •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).

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)
windows.microsoft.com301 → https://go.microsoft.com/fwlink/p/ → … → https://www.microsoft.com/en-gb/windows/ → 200 OK301 → https://go.microsoft.com/fwlink/p/ → … → https://www.microsoft.com/en-gb/windows/ → 200 OK
  • http://windows.microsoft.com redirects to HTTPS.
  • https://windows.microsoft.com forwards visitors to go.microsoft.com, a different site. View its report ›

DNS Records

As a public resolver answered for windows.microsoft.com and its domain microsoft.com. Looked up 2026-11-22 14:40 UTC · today

TypeRecords
windows.microsoft.com
A
AAAA None
MX None
SPF None
microsoft.com
A
AAAA
NS
ns1-39.azure-dns.com ns2-39.azure-dns.net ns3-39.azure-dns.org ns4-39.azure-dns.info
MX
10 microsoft-com.mail.protection.outlook.com
SPF
v=spf1 include:_spf-a.microsoft.com include:_spf-b.microsoft.com include:_spf-ssg-a.msft.net include:_spf1-meo.microsoft.com -all

Certificate Identity

Common Namewindows.microsoft.com
Alt Names windows.microsoft.com redir.windows.microsoft.com s-res.s.windows.microsoft.com s.windows.microsoft.com
IssuerCN=Microsoft TLS G2 RSA CA OCSP 16, O=Microsoft Corporation, C=US
Validity 2026-01-22 to 2027-01-17 (56 days remaining)
KeyRSA 2048 bits (sha384RSA)
Serial Number550003785B8CFED209B4C9E47600000003785B
SHA256 Fingerprint b12caff23182db8c097a6a62ca542442e4a110a0acc5969232e5222a87104cb7
Pin SHA256rhFviSQl2YVObY3VfXf8E6pLtACnSL+his4GvYtzKOE=

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%2016_Partition00019.crl
DNS CAA Yes (configured) 0 contactemail "[email protected]"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 360 days (maximum 398 days for certificates issued then)
Chain IssuesNone

Protocol Configuration

Supported Protocols

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

Negotiated Cipher

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN http/1.1
SNI Required No
Supported Named Groups secp256r1 (inferred)
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 (TLS_FALLBACK_SCSV)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling Yes
HSTS Unknown (the HTTPS request to this IP failed)
HSTS Preloading N/A (HSTS not enabled)
Security Checks
BEAST attack Not mitigated server-side (TLS 1.0 + CBC)
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) Possible (CBC + legacy TLS present)
RC4 Yes (RC4 cipher enabled)
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.2 (server-preferred order)
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_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_3DES_EDE_CBC_SHA0x000ARSANo FS112Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_RC4_128_SHA0x0005RSANo FS128Insecure
TLS_RSA_WITH_RC4_128_MD50x0004RSANo FS128Insecure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
macOS 14 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 14TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 4.0.4TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success
Android 4.1.1TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success
Baidu Jan 2015TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success
Java 6TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success

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

Trust Chain Architecture

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

Certificates served

Certificate (SHA-256)IssuerValidServed
b12caff23182db8c… current Microsoft TLS G2 RSA CA OCSP 162026-01-22 → 2027-01-172026-11-22

Addresses

AddressCertificateSeen
2.18.143.160 b12caff23182db8c… 2026-11-22

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 14:40CTLS 1.2 b12caff23182db8c… 2.18.143.160