SSL Check WHOIS
Dashboard / Security Report

login.windows.net

Overall grade based on: IPv4: 8 of 8 complete · IPv6: 0 of 4 complete, 4 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2603:1026:3000:108::3 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2603:1026:3000:108::7 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2603:1026:3000:118::3 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2603:1027:1:108::7 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 8 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 20.190.181.0 IPv4 WHOIS › A+ 20.190.181.1 IPv4 WHOIS › A+ 20.190.181.5 IPv4 WHOIS › A+ 20.190.181.6 IPv4 WHOIS › A+ 40.126.53.15 IPv4 WHOIS › A+ 40.126.53.19 IPv4 WHOIS › A+ 40.126.53.21 IPv4 WHOIS › A+ 40.126.53.8 IPv4 WHOIS ›

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 No
SNI Required Yes
Supported Named Groups 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 Not preloadedSubmit →
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_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak

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)
login.windows.net302 → https://login.windows.net/ → … → https://login.microsoftonline.com/common/oauth2/v2.0/authorize → 200 OK302 → https://www.office.com/login → … → https://login.microsoftonline.com/common/oauth2/v2.0/authorize → 200 OK
  • http://login.windows.net redirects to HTTPS.
  • https://login.windows.net forwards visitors to www.office.com, a different site. View its report ›

Certificate Identity

Common Namelogin.windows.net
Alt Names login.windows.net *.accesscontrol.windows-ppe.net *.accesscontrol.windows.net *.mtlsauth.microsoft.com *.mtlsauth.windows-ppe.net *.windows-ppe.net device.login.microsoftonline.com device.login.windows-ppe.net geo.login.windows-ppe.net geo.logincert.microsoftonline.com iotauth.microsoft.com login-us.microsoftonline.com login.microsoft-ppe.com login.microsoft.com login.microsoftonline-p-int.com login.microsoftonline-p.com login.microsoftonline.com logincert.microsoftonline-int.com logincert.microsoftonline.com logincert.windows-ppe.net mtlsauth.microsoft.com mtlsauth.windows-ppe.net sts.windows.net
IssuerCN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Validity 2026-10-16 to 2027-01-24 (68 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0AF36DCF8D3D2BB9A2C670600C7D8F39
SHA256 Fingerprint e2da818dddcf0f13fccbde05711d657a4df8055cf681da6c7abb05ef634181bc
Pin SHA256JN1xt7GpjpaLzGIp9DGzChH7RPe0EGWHGRk6I6RaTMU=

Certificate Properties

Type OV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Unknown (CRL could not be downloaded) OCSP: http://ocsp.digicert.com CRL: http://crl3.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl
DNS CAA Yes (configured) 0 contactemail "[email protected]"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 101 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=login.windows.net, O=Microsoft Corporation, L=Redmond, S=Washington, C=US (Issuer: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US)
Intermediate CA
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, 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 login.windows.net, first seen 2026-11-03; current certificate since 2026-11-05.

Certificates served

Certificate (SHA-256)IssuerValidServed
e2da818dddcf0f13… current DigiCert Global G2 TLS RSA SHA256 2020 CA12026-10-16 → 2027-01-242026-11-05

Addresses

AddressCertificateSeen
20.190.181.0 e2da818dddcf0f13… 2026-11-05
20.190.181.1 e2da818dddcf0f13… 2026-11-05
20.190.181.5 e2da818dddcf0f13… 2026-11-05
20.190.181.6 e2da818dddcf0f13… 2026-11-05
40.126.53.8 e2da818dddcf0f13… 2026-11-05
40.126.53.15 e2da818dddcf0f13… 2026-11-05
40.126.53.19 e2da818dddcf0f13… 2026-11-05
40.126.53.21 e2da818dddcf0f13… 2026-11-05

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-05 18:54A+TLS 1.3 e2da818dddcf0f13… 20.190.181.0, 20.190.181.1, 20.190.181.5, 20.190.181.6, 40.126.53.8, 40.126.53.15, 40.126.53.19, 40.126.53.21

Other domains on the same certificate

Other hosts seen on the same addresses