TLS/SSL check of 'www.bing.com (150.171.28.10)'

Multiple A-records!

The domain 'www.bing.com' has severals A/AAAA-records - and thereby multiple IP's to check.

click to use
150.171.27.10

Summary


Host:
www.bing.com, 150.171.28.10, port 443


Protocols:
All good
 2 supported protocols: TLS 1.3, TLS 1.2


Certificate:
All good
 Certificate 'www.bing.com, Microsoft Corporation, US' is verified okay. Issued by 'Microsoft Azure RSA TLS Issuing CA 07'. Expires 2025-09-10.

Protocol support



Protocol support:
TLS 1.3
Supported
TLS 1.2
Supported
TLS 1.1
No support
TLS 1.0
No support
SSL 3.0
No support
SSL 2.0
No support

Verification:
TLS 1.3 is supported
 

Chain of certificates

3 of 3 - End-Entity
www.bing.com


Certificat:
www.bing.com, Microsoft Corporation, US

Issued by:
Microsoft Azure RSA TLS Issuing CA 07, Microsoft Corporation, US

Valid:
From 2025-03-14 to 2025-09-10

Verification:
Certificate is verified okay

SAN's:
*.platform.bing.com
*.bing.com
bing.com
ieonline.microsoft.com
*.windowssearch.com
cn.ieonline.microsoft.com
*.origin.bing.com
*.mm.bing.net
*.api.bing.com
*.cn.bing.net
*.cn.bing.com
ssl-api.bing.com
ssl-api.bing.net
*.api.bing.net
*.bingapis.com
bingsandbox.com
feedback.microsoft.com
insertmedia.bing.office.net
r.bat.bing.com
*.r.bat.bing.com
*.dict.bing.com
*.ssl.bing.com
*.appex.bing.com
*.platform.cn.bing.com
wp.m.bing.com
*.m.bing.com
global.bing.com
windowssearch.com
search.msn.com
*.bingsandbox.com
*.api.tiles.ditu.live.com
*.t0.tiles.ditu.live.com
*.t1.tiles.ditu.live.com
*.t2.tiles.ditu.live.com
*.t3.tiles.ditu.live.com
3d.live.com
api.search.live.com
beta.search.live.com
cnweb.search.live.com
ditu.live.com
farecast.live.com
image.live.com
images.live.com
local.live.com.au
localsearch.live.com
ls4d.search.live.com
mail.live.com
mapindia.live.com
local.live.com
maps.live.com
maps.live.com.au
mindia.live.com
news.live.com
origin.cnweb.search.live.com
preview.local.live.com
search.live.com
test.maps.live.com
video.live.com
videos.live.com
virtualearth.live.com
wap.live.com
webmaster.live.com
www.local.live.com.au
www.maps.live.com.au
webmasters.live.com
ecn.dev.virtualearth.net
www.bing.com

Key:
RSA, 2048 bit
Signature algorithm:
sha384RSA

Serial:
3301974591BE2869F9D9EF8732000001974591

PEM format:

2 of 3 - Intermediate
Microsoft Azure RSA TLS Issuing CA 07


Certificat:
Microsoft Azure RSA TLS Issuing CA 07, Microsoft Corporation, US

Issued by:
DigiCert Global Root G2, DigiCert Inc, US

Valid:
From 2023-06-08 to 2026-08-25

Verification:
Certificate is verified okay

Key:
RSA, 4096 bit
Signature algorithm:
sha384RSA

Serial:
0A43A9509B01352F899579EC7208BA50

PEM format:

1 of 3 - Root certificate
DigiCert Global Root G2


Certificat:
DigiCert Global Root G2, DigiCert Inc, US

Issued by:
DigiCert Global Root G2, DigiCert Inc, US

Valid:
From 2013-08-01 to 2038-01-15

Verification:
Certificate is verified okay

Key:
RSA, 2048 bit
Signature algorithm:
sha256RSA

Serial:
033AF1E6A711A9A0BB2864B11D09FAE5

PEM format:

Root Store trust

DigiCert Global Root G2


Issued by:
DigiCert

Root Store trust:
The root certificte is trustet by ALL major trusted root certificate stores

Microsoft:
Root Certificate is fully trusted by Microsoft (Windows)

Apple:
Root Certificate is fully is trusted by Apple (iOS, iPadOS, macOS)

Android:
Root Certificate is fully is trusted by Android

API

You may perform this lookup using the API and get the results as easy-to-parse JSON data.

Read more on the API at https://iamroot.tech/about/api (regarding authentication and rate limits, among other things), or give it a go right away using the 'try it' button.

 
GET
https://iamroot.tech/ssl-certificate-check/api/?host=www.bing.com&hostPort= copy try it
 

Log

010+010
  • Host 'www.bing.com' resolved in 9ms
010+000
  • INFMultiple A-records!
    Domain 'www.bing.com' has several A-records, and thereby multiple IPs to check. IP 150.171.28.10 will be used.
010+000
  • Check protocols
010+000
  • Start SSL 2.0 protocol check, www.bing.com (150.171.28.10), port 443
010+000
  • Start TLS 1.3 protocol check, www.bing.com (150.171.28.10), port 443
011+000
  • Start TLS 1.2 protocol check, www.bing.com (150.171.28.10), port 443
011+000
  • Start TLS 1.1 protocol check, www.bing.com (150.171.28.10), port 443
011+000
  • Start TLS 1.0 protocol check, www.bing.com (150.171.28.10), port 443
011+000
  • Start SSL 3.0 protocol check, www.bing.com (150.171.28.10), port 443
019+008
  • Protocol check of SSL 3.0 done in 8ms - failed
    Unable to authenticate connection using SSL 3.0
019+009
  • Protocol check of SSL 2.0 done in 8ms - failed
    Unable to authenticate connection using SSL 2.0
029+018
  • Protocol check of TLS 1.0 done in 18ms - failed
    Unable to authenticate connection using TLS 1.0
029+019
  • Protocol check of TLS 1.1 done in 18ms - failed
    Unable to authenticate connection using TLS 1.1
040+030
  • Protocol check of TLS 1.2 done in 29ms - all good
041+031
  • Protocol check of TLS 1.3 done in 30ms - all good
041+022
  • TLS 1.3 is supported
041+000
  • Done
041+000
  • Check certificate
041+000
  • Load and verify chain of certificates
174+133
  • Full chain of certificates has been loaded and verified in 132ms.
174+000
  • End-Entity certificate verification success
    Certificat 'www.bing.com' SUCCEDED the verification.
174+000
  • Host 'www.bing.com' is matching Subject/SAN 'www.bing.com' of certificate. All good!
174+000
  • Intermediate certificate verification success
    Certificat 'Microsoft Azure RSA TLS Issuing CA 07' SUCCEDED the verification.
174+000
  • Root certificate verification success
    Certificat 'DigiCert Global Root G2' SUCCEDED the verification.
174+000
  • Check root store status of root certificate
175+001
  • Trustet by all major trusted root certificate stores
    The root certificte is trustet by ALL major trusted root certificate stores
175+000
  • Done
175+000
  • Done
175+000
  • Done