SSL Check WHOIS
Dashboard / Security Report

pulse.cloud.microsoft

Overall grade based on: IPv4: 1 of 1 complete · IPv6: 0 of 1 complete, 1 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2603:1061:14:21::1 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.

A+

Exceptional Security

Overall Rating
150.171.109.33 · WHOIS ›
Assessed 2026-10-31 15:14 UTC

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.

Hosthttp:// (port 80)https:// (port 443)
pulse.cloud.microsoft400 Bad Request (unencrypted)200 OK
  • http://pulse.cloud.microsoft answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.

Certificate Identity

Common Namepulse.cloud.microsoft
Alt Names pulse.cloud.microsoft
IssuerCN=Microsoft TLS G2 RSA CA OCSP 16, O=Microsoft Corporation, C=US
Validity 2026-10-11 to 2027-01-19 (63 days remaining)
KeyRSA 2048 bits (sha384RSA)
Serial Number55012AAC5DB5ADD3A577348F520000012AAC5D
SHA256 Fingerprint 62de15613579fa7dddec371fce48bcd886e0ea68e41847a8bb5b329768bce0c9
Pin SHA2567DamdeUwhvdfM+a0tTcoLvI/EhxBDoKhtAvM05L3ycM=

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%20RSA%20CA%20OCSP%2016_Partition00077.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 100 days (maximum 200 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

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 SecP256r1MLKEM768 X25519MLKEM768 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes SecP256r1MLKEM768, 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 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 (server-preferred order)
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# 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_128_CBC_SHA2560xC027ECDHEFS128Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.3TLS_AES_256_GCM_SHA384 Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384 Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256 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.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=pulse.cloud.microsoft, 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 pulse.cloud.microsoft, first seen 2026-10-31; current certificate since 2026-10-31.

Certificates served

Certificate (SHA-256)IssuerValidServed
62de15613579fa7d… current Microsoft TLS G2 RSA CA OCSP 162026-10-11 → 2027-01-192026-10-31

Addresses

AddressCertificateSeen
150.171.109.33 62de15613579fa7d… 2026-10-31

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-31 15:14A+TLS 1.3 62de15613579fa7d… 150.171.109.33

Other hosts seen on the same addresses