SSL Check WHOIS
Dashboard / Security Report

www.bing.com

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

www.bing.com: SSL/TLS grade A+ (HTTPS Monitor)www.bing.comA+
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
2a02:26f0:3900::1729:b219 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:3900::1729:b21a IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:3900::1729:b21b IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:3900::1729:b223 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+ 2.17.197.107 IPv4 WHOIS › A+ 2.17.197.112 IPv4 WHOIS › A+ 2.17.197.115 IPv4 WHOIS › A+ 2.17.197.128 IPv4 WHOIS › A+ 2.17.197.131 IPv4 WHOIS › A+ 2.17.197.138 IPv4 WHOIS › A+ 2.17.197.145 IPv4 WHOIS › A+ 2.17.197.160 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 X25519MLKEM768 x25519 secp256r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768
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 Yes 1 year · includeSubDomains · preload
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
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_128_CCM_SHA2560x1304ECDHEFS128Secure
# TLS 1.2
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
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

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_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_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)
www.bing.com200 OK (unencrypted)200 OK
bing.com301 → http://www.bing.com/ → 200 OK301 → https://www.bing.com/ → 200 OK
  • http://www.bing.com answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.

DNS Records

As a public resolver answered for www.bing.com and its domain bing.com. Looked up 2026-11-20 20:59 UTC · 1 day ago

TypeRecords
www.bing.com
A
AAAA
MX None
SPF None
bing.com
A
AAAA
NS
dns1.p09.nsone.net dns2.p09.nsone.net dns3.p09.nsone.net dns4.p09.nsone.net ns1-204.azure-dns.com ns2-204.azure-dns.net ns3-204.azure-dns.org ns4-204.azure-dns.info
MX
10 bing-com.mail.protection.outlook.com
SPF
v=spf1 include:spf.protection.outlook.com -all

Certificate Identity

Common Namewww.bing.com
Alt Names *.bing.com *.bingstatic.com *.explicit.bing.net *.mm.bing.net akam.bing.com r.bing.com r.msftstatic.com raka.bing.com raka.msftstatic.com th.bing.com th.msftstatic.com thaka.bing.com thaka.msftstatic.com
IssuerCN=Microsoft TLS G2 ECC CA OCSP 02, O=Microsoft Corporation, C=US
Validity 2026-11-05 to 2027-05-22 (180 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number57000B004E949B32DA25FB7CE60000000B004E
SHA256 Fingerprint f8ba727ec7af619094ffd48e4dcabc39ef662fa6d1d2ea48602d676e607c2800
Pin SHA256rrK/86KB9PhxGdmVwUV3C026wyj0QqsCu2+od2jmMIY=

Certificate Properties

Type OV Organization Validated
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_Partition00093.crl
DNS CAA Yes (configured) 0 contactemail "[email protected]" 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "microsoft.com"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=r.bing.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 www.bing.com, first seen 2026-04-13; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
f8ba727ec7af6190… current Microsoft TLS G2 ECC CA OCSP 022026-11-05 → 2027-05-222026-11-19 → 2026-11-20
af43b6f9b44ce0a9… Microsoft TLS G2 ECC CA OCSP 022026-09-17 → 2027-04-032026-10-04

Addresses

AddressCertificateSeen
2.17.197.107 f8ba727ec7af6190… 2026-11-20
2.17.197.112 f8ba727ec7af6190… 2026-11-20
2.17.197.115 f8ba727ec7af6190… 2026-11-20
2.17.197.128 f8ba727ec7af6190… 2026-11-20
2.17.197.131 f8ba727ec7af6190… 2026-11-19 → 2026-11-20
2.17.197.138 f8ba727ec7af6190… 2026-11-19 → 2026-11-20
2.17.197.145 f8ba727ec7af6190… 2026-11-20
2.17.197.160 f8ba727ec7af6190… 2026-11-19 → 2026-11-20
2.17.197.123 f8ba727ec7af6190… 2026-11-19
2.17.197.136 f8ba727ec7af6190… 2026-11-19
2.17.197.146 f8ba727ec7af6190… 2026-11-19
2.17.197.152 f8ba727ec7af6190… 2026-11-19
2.17.197.155 f8ba727ec7af6190… 2026-11-19
92.123.128.133 af43b6f9b44ce0a9… 2026-10-04
92.123.128.146 af43b6f9b44ce0a9… 2026-10-04
92.123.128.147 af43b6f9b44ce0a9… 2026-10-04
92.123.128.161 af43b6f9b44ce0a9… 2026-10-04
92.123.128.167 af43b6f9b44ce0a9… 2026-10-04
92.123.128.169 af43b6f9b44ce0a9… 2026-10-04
92.123.128.181 af43b6f9b44ce0a9… 2026-10-04
92.123.128.187 af43b6f9b44ce0a9… 2026-10-04

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-20 20:59A+TLS 1.3 f8ba727ec7af6190… 2.17.197.107, 2.17.197.112, 2.17.197.115, 2.17.197.128, 2.17.197.131, 2.17.197.138, 2.17.197.145, 2.17.197.160
2026-11-19 10:33A+TLS 1.3 f8ba727ec7af6190… 2.17.197.123, 2.17.197.131, 2.17.197.136, 2.17.197.138, 2.17.197.146, 2.17.197.152, 2.17.197.155, 2.17.197.160
2026-10-04 00:54A+TLS 1.3 af43b6f9b44ce0a9… 92.123.128.133, 92.123.128.146, 92.123.128.147, 92.123.128.161, 92.123.128.167, 92.123.128.169, 92.123.128.181, 92.123.128.187

Other domains on the same certificate

Other hosts seen on the same addresses