devblogs.microsoft.com
Overall grade based on: IPv4: 1 of 1 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
2a02:26f0:9100:1592::2f1e IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:9100:1593::2f1e 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.
Grade Breakdown
Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| devblogs.microsoft.com | 301 → https://devblogs.microsoft.com/ → 200 OK | 200 OK |
- http://devblogs.microsoft.com redirects to HTTPS.
Certificate Identity
| Common Name | devblogs.microsoft.com |
| Alt Names | devblogs.microsoft.com www.devblogs.microsoft.com |
| Issuer | CN=Microsoft TLS G2 ECC CA OCSP 02, O=Microsoft Corporation, C=US |
| Validity | 2026-09-22 to 2027-04-08 (142 days remaining) |
| Key | ECDSA 256 bits (sha384ECDSA) |
| Serial Number | 5700076B4273C2BED59902A8BD000000076B42 |
| SHA256 Fingerprint | 0c33a5c48f09502c20a1b9702dc151146da4b09a280b8baabac4834ea5f4a73f |
| Pin SHA256 | NQK4FFf3J4eA/tVKE8keetbJY+PbIEFTSVGCxRwMI+0= |
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%20ECC%20CA%20OCSP%2002_Partition00051.crl |
| DNS CAA | Yes (configured) 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 Issues | None |
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 | No |
| Supported Named Groups | X25519MLKEM768 x25519 secp256r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768 |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (legacy TLS disabled) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | Yes |
| HSTS | Yes 182 days · includeSubDomains · preload |
| HSTS Preloading | Not preloadedSubmit → |
| Security Checks | |
| BEAST attack | Mitigated |
| POODLE (SSLv3) | No (SSL 3 not supported) |
| POODLE (TLS) | No |
| RC4 | No |
| SSL/TLS Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 (server-preferred order) | |||||
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_128_CCM_SHA256 | 0x1304 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 (server-preferred order) | |||||
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | 0xC02C | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 0xC02B | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA9 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 | 0xC024 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 | 0xC023 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA256 | 0x003D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x003C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA | 0x0035 | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA | 0x002F | RSA | No FS | 128 | Weak |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| 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.
Trust Chain Architecture
End-Entity Certificate
CN=devblogs.microsoft.com, O=Microsoft Corporation, L=Redmond, S=WA, C=US (Issuer: CN=Microsoft TLS G2 ECC CA OCSP 02, O=Microsoft Corporation, C=US)
Intermediate CA
CN=Microsoft TLS G2 ECC CA OCSP 02, O=Microsoft Corporation, C=US (Issuer: CN=Microsoft TLS ECC Root G2, O=Microsoft Corporation, C=US)
Intermediate CA
CN=Microsoft TLS ECC Root G2, O=Microsoft Corporation, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
TLS History & Relations
Everything our scans have seen for devblogs.microsoft.com, first seen 2026-10-26; current certificate since 2026-10-26.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 0c33a5c48f09502c… current | Microsoft TLS G2 ECC CA OCSP 02 | 2026-09-22 → 2027-04-08 | 2026-10-26 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 23.39.250.161 | 0c33a5c48f09502c… | 2026-10-26 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-10-26 15:11 | A+ | TLS 1.3 | 0c33a5c48f09502c… | 23.39.250.161 |