www.office.com
Overall grade based on: IPv4: 2 of 2 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
2603:1061:10:1::13 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2603:1061:10::13 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 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 150.171.73.13 IPv4 WHOIS › A+ 150.171.74.13 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 | h2 http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | secp521r1 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 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 | 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 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 | |||||
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 | |||||
| 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_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 | 0x009F | DHE | FS | 256 | Secure |
| TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | 0x009E | DHE | FS | 128 | Secure |
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_AES_256_GCM_SHA384 | 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_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_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.
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) |
|---|---|---|
| www.office.com | 301 → http://m365.cloud.microsoft/ → … → https://m365.cloud.microsoft/ → 200 OK | 301 → https://m365.cloud.microsoft/ → 200 OK |
| office.com | 301 → https://www.office.com/ → … → https://m365.cloud.microsoft/ → 200 OK | 301 → https://www.office.com/ → … → https://m365.cloud.microsoft/ → 200 OK |
- http://www.office.com redirects to HTTPS.
- https://www.office.com forwards visitors to m365.cloud.microsoft, a different site. View its report ›
DNS Records
As a public resolver answered for www.office.com and its domain office.com. Looked up 2026-11-17 22:04 UTC · today
| Type | Records |
|---|---|
| www.office.com | |
| A | |
| AAAA | |
| MX | None |
| SPF | None |
| office.com | |
| A | |
| AAAA | |
| NS | ns1-05.azure-dns.com ns2-05.azure-dns.net ns3-05.azure-dns.org ns4-05.azure-dns.info |
| MX | None |
| SPF | None |
Certificate Identity
| Common Name | www.office.com |
| Alt Names | home.office.com login.office.com office.com signin.office.com www.office.com *.www.office.com word.office.com excel.office.com powerpoint.office.com visio.office.com apps.office.com stream.office.com fluid.office.com www.microsoft365.com m365.go.microsoft m365.cloud.microsoft ntp.www.office.com microsoft365.com *.www.microsoft365.com copilot.cloud.microsoft |
| Issuer | CN=Microsoft TLS G2 RSA CA OCSP 04, O=Microsoft Corporation, C=US |
| Validity | 2026-10-13 to 2027-01-21 (64 days remaining) |
| Key | RSA 2048 bits (sha384RSA) |
| Serial Number | 4301478A3A6E4E3826CC8AB97B000001478A3A |
| SHA256 Fingerprint | 944d071fb0f69a0cb04a7d6765dc694868f47d258957b5845a1edf3702259897 |
| Pin SHA256 | E/wio+zQS7DAW5QjNOakKe1BW3DTx1K7ELHPNIgJGbI= |
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%2004_Partition00004.crl |
| DNS CAA | Yes (configured) 0 iodef "mailto:[email protected]" 0 issue "digicert.com" 0 issue "dtrust.de" 0 issue "entrust.net" 0 issue "globalsign.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 | None |
Trust Chain Architecture
End-Entity Certificate
CN=m365.cloud.microsoft, O=Microsoft Corporation, L=Redmond, S=WA, C=US (Issuer: CN=Microsoft TLS G2 RSA CA OCSP 04, O=Microsoft Corporation, C=US)
Intermediate CA
CN=Microsoft TLS G2 RSA CA OCSP 04, 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 www.office.com, first seen 2026-06-09; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 944d071fb0f69a0c… current | Microsoft TLS G2 RSA CA OCSP 04 | 2026-10-13 → 2027-01-21 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 150.171.73.13 | 944d071fb0f69a0c… | 2026-11-17 |
| 150.171.74.13 | 944d071fb0f69a0c… | 2026-11-17 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-17 22:04 | A+ | TLS 1.3 | 944d071fb0f69a0c… | 150.171.73.13, 150.171.74.13 |
Other domains on the same certificate
- microsoft365.com 3 names www.microsoft365.com *.www.microsoft365.com
- cloud.microsoft 2 names
- go.microsoft 1 name