SSL Check WHOIS
Dashboard / Security Report

datacenters.microsoft.com

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 141.193.213.20 IPv4 WHOIS › A+ 141.193.213.21 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-17 21:27 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 X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
HTTP/3 (QUIC) Yes (advertised)
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 No
HSTS Preloading N/A (HSTS not enabled)
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_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak

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_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
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)
datacenters.microsoft.com301 → https://datacenters.microsoft.com/ → 200 OK200 OK
  • http://datacenters.microsoft.com redirects to HTTPS.

DNS Records

As a public resolver answered for datacenters.microsoft.com and its domain microsoft.com. Looked up 2026-11-17 21:27 UTC · today

TypeRecords
datacenters.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 Namedatacenters.microsoft.com
Alt Names datacenters.microsoft.com
IssuerCN=Cloudflare TLS Issuing ECC CA 3, O=SSL Corporation, C=US
Validity 2026-09-27 to 2026-12-26 (38 days remaining)
KeyECDSA 256 bits (sha256ECDSA)
Serial Number1119B57A38642A9F4DF0215272C506F7
SHA256 Fingerprint a7128eb455da948de5c559db6e749fcfb11f2612d8b52d68c7fdd4861335ee02
Pin SHA256HiMiGTq4ic6m7DrMlWltEohBOaUy6Q+1xvWAaUSveS0=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://o.cf-i.ssl.com CRL: http://c.cf-i.ssl.com/ae801ed1c55bb579d79208b0d772acfb8cc3a208.crl
DNS CAA Yes (configured) 0 contactemail "[email protected]"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 90 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=datacenters.microsoft.com (Issuer: CN=Cloudflare TLS Issuing ECC CA 3, O=SSL Corporation, C=US)
Intermediate CA
CN=Cloudflare TLS Issuing ECC CA 3, O=SSL Corporation, C=US (Issuer: CN=SSL.com TLS Transit ECC CA R2, O=SSL Corporation, C=US)
Intermediate CA
CN=SSL.com TLS Transit ECC CA R2, O=SSL Corporation, C=US (Issuer: CN=SSL.com TLS ECC Root CA 2022, O=SSL Corporation, C=US)
Root Certificate
CN=SSL.com TLS ECC Root CA 2022, O=SSL Corporation, C=US (Issuer: CN=SSL.com TLS ECC Root CA 2022, O=SSL Corporation, C=US)

TLS History & Relations

Everything our scans have seen for datacenters.microsoft.com, first seen 2026-11-17; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
a7128eb455da948d… current Cloudflare TLS Issuing ECC CA 32026-09-27 → 2026-12-262026-11-17

Addresses

AddressCertificateSeen
141.193.213.20 a7128eb455da948d… 2026-11-17
141.193.213.21 a7128eb455da948d… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 21:27A+TLS 1.3 a7128eb455da948d… 141.193.213.20, 141.193.213.21

Other hosts seen on the same addresses