TLS/SSL certificate check


Port to connect on:
Secure HTTP / HTTPS - port 443 Secured SMTP - port 465 Secured IMAP - port 993 Secured POP3 - port 995

TLS/SSL check of 'dual-a-0001.a-msedge.net (2620:1ec:c11::200)'

Multiple A-records!

The domain 'dual-a-0001.a-msedge.net' has severals A/AAAA-records - and thereby multiple IP's to check.

click to use
13.107.21.200
click to use
204.79.197.200

Host verification error

Host 'dual-a-0001.a-msedge.net' is NOT among the specified subjects of the certificate - therfore the certificate can not be used to authenticate the connection.

Summary


Host:
dual-a-0001.a-msedge.net, 2620:1ec:c11::200, port 443


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


Certificate:
Failed
 Certificate 'www.bing.com': Host verification error

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 TLS Issuing CA 02, Microsoft Corporation, US

Valid:
From 2024-04-30 to 2024-06-27

Verification:
Host verification error
 
Host 'dual-a-0001.a-msedge.net' is NOT among the specified subjects of the certificate - therfore the certificate can not be used to authenticate the connection.

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:
3300F04C6B1F6F1E7A52D9655C000000F04C6B

PEM format:
Click to see certificate as PEM (modal)

2 of 3 - Intermediate
Microsoft Azure TLS Issuing CA 02

Certificat:
Microsoft Azure TLS Issuing CA 02, Microsoft Corporation, US

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

Valid:
From 2020-07-29 to 2024-06-27

Verification:
Certificate is verified okay

Key:
RSA, 4096 bit
Signature algorithm:
sha384RSA

Serial:
0C6AE97CCED599838690A00A9EA53214

PEM format:
Click to see certificate as PEM (modal)

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:
Click to see certificate as PEM (modal)

Root Store trust

Root Certificat:
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=dual-a-0001.a-msedge.net copy try it
 

Log

037+037
  • Host 'dual-a-0001.a-msedge.net' resolved in 36ms
037+000
  • INFMultiple A-records!
    Domain 'dual-a-0001.a-msedge.net' has several A-records, and thereby multiple IPs to check. IP 2620:1ec:c11::200 will be used.
037+000
  • Check protocols
037+000
  • Start SSL 2.0 protocol check, dual-a-0001.a-msedge.net (2620:1ec:c11::200), port 443
037+000
  • Start TLS 1.3 protocol check, dual-a-0001.a-msedge.net (2620:1ec:c11::200), port 443
037+000
  • Start TLS 1.2 protocol check, dual-a-0001.a-msedge.net (2620:1ec:c11::200), port 443
037+000
  • Start TLS 1.1 protocol check, dual-a-0001.a-msedge.net (2620:1ec:c11::200), port 443
038+000
  • Start TLS 1.0 protocol check, dual-a-0001.a-msedge.net (2620:1ec:c11::200), port 443
038+000
  • Start SSL 3.0 protocol check, dual-a-0001.a-msedge.net (2620:1ec:c11::200), port 443
048+010
  • Protocol check of SSL 3.0 done in 10ms - failed
    Unable to authenticate connection using SSL 3.0
048+011
  • Protocol check of SSL 2.0 done in 10ms - failed
    Unable to authenticate connection using SSL 2.0
057+019
  • Protocol check of TLS 1.1 done in 19ms - failed
    Unable to authenticate connection using TLS 1.1
057+019
  • Protocol check of TLS 1.0 done in 18ms - failed
    Unable to authenticate connection using TLS 1.0
079+042
  • Protocol check of TLS 1.3 done in 41ms - all good
079+042
  • Protocol check of TLS 1.2 done in 42ms - all good
080+031
  • TLS 1.3 is supported
080+000
  • Done
080+000
  • Check certificate
080+000
  • Load and verify chain of certificates
309+230
  • Full chain of certificates has been loaded and verified in 229ms.
309+000
  • End-Entity certificate verification success
    Certificat 'www.bing.com' SUCCEDED the verification.
310+000
  • ERRHost verification error
    Host 'dual-a-0001.a-msedge.net' is NOT among the specified subjects of the certificate - therfore the certificate can not be used to authenticate the connection.
310+000
  • Intermediate certificate verification success
    Certificat 'Microsoft Azure TLS Issuing CA 02' SUCCEDED the verification.
310+000
  • Root certificate verification success
    Certificat 'DigiCert Global Root G2' SUCCEDED the verification.
310+000
  • Check root store status of root certificate
311+001
  • Trustet by all major trusted root certificate stores
    The root certificte is trustet by ALL major trusted root certificate stores
311+000
  • Done
311+000
  • Done
311+000
  • Done
New features inbound 🚀
Within a couple of weeks, I'll launch a couple of new awesome features. Signup for the newsletter to stay updated, and get early access as a beta tester.

Signup using Google, Microsoft or Facebook .