SSL Check WHOIS
Dashboard / Security Report

m.bncd.ca

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 2.17.197.107 IPv4 WHOIS › A+ 2.17.197.147 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-11 22:51 UTC

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) 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
HSTS Preloading Not preloadedSubmit →
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_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
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_RSA_WITH_AES_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_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)
m.bncd.ca301 → http://bncd.ca/ → … → https://www.nbc.ca/fr/courtage-direct.html → 200 OK301 → https://bncd.ca/ → … → https://www.nbc.ca/fr/courtage-direct.html → 200 OK
  • http://m.bncd.ca redirects to HTTPS.
  • https://m.bncd.ca forwards visitors to bncd.ca, a different site. View its report ›

DNS Records

As a public resolver answered for m.bncd.ca and its domain bncd.ca. Looked up 2026-11-11 22:51 UTC · 5 days ago

TypeRecords
m.bncd.ca
A
AAAA None
MX None
SPF None
bncd.ca
A
AAAA None
NS
a1-62.akam.net a10-65.akam.net a26-66.akam.net a4-67.akam.net a5-64.akam.net a7-65.akam.net
MX None
SPF
v=spf1 -all

Certificate Properties

Type OV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.globalsign.com/ca/gsatlasr46ovtlsca2026q3 CRL: http://crl.globalsign.com/ca/gsatlasr46ovtlsca2026q3.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 199 days (maximum 200 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

Trust Chain Architecture

End-Entity Certificate
CN=mig.bncd.ca, O=Banque Nationale du Canada, L=Montreal, S=Quebec, C=CA (Issuer: CN=GlobalSign Atlas R46 OV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE)
Intermediate CA
CN=GlobalSign Atlas R46 OV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)
Root Certificate
CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)

TLS History & Relations

Everything our scans have seen for m.bncd.ca, first seen 2026-11-09; current certificate since 2026-11-11.

Certificates served

Certificate (SHA-256)IssuerValidServed
4e3191df642e78a2… current GlobalSign Atlas R46 OV TLS CA 2026 Q32026-08-10 → 2027-02-252026-11-11

Addresses

AddressCertificateSeen
2.17.197.107 4e3191df642e78a2… 2026-11-11
2.17.197.147 4e3191df642e78a2… 2026-11-11

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-11 22:51A+TLS 1.3 4e3191df642e78a2… 2.17.197.107, 2.17.197.147

Other domains on the same certificate

Other hosts seen on the same addresses