You are here: Home > Projects > SSL Server Test >imformuat.idfcfirstbank.com
SSL Report: imformuat.idfcfirstbank.com (152.67.2.62)
Assessed on: Wed, 24 Apr 2024 04:57:59 UTC | Clear cache
Scan Another»
Summary
See Also
Faster Post-Quantum TLS 1.3 Based on ML-KEM: Implementation and Assessmentconfig load-balance client-ssl-profile | CLI Referencezeitungen.sub.uni-hamburg.de (Powered by Qualys SSL Labs)Overall Rating
T
If trust issues are ignored: B
20
40
60
80
100
Certificate
Protocol Support
Key Exchange
Cipher Strength
Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
This server's certificate is not trusted, see below for details.
This server's certificate is not trusted by major browsers. MOREINFO»
This server's certificate chain is incomplete. Grade capped to B.
This server supports TLS 1.3.
Certificate #1: RSA 2048 bits (SHA256withRSA)
| Server Key and Certificate #1 | |
| Subject | imformuat.idfcfirstbank.com Fingerprint SHA256: 42ee45fd01ea54c6837b2ee9dfdfcf8fd5c18382296f5f0d02f981af11d53cef Pin SHA256: bN24v4RvnPAgGYmBQR6g5oEk5Fwx2pVlS+YmvTYr0mk= |
| Common names | imformuat.idfcfirstbank.com |
| Alternative names | imformuat.idfcfirstbank.com |
| Serial Number | 7e00025855d36bc1a4663bdce6000100025855 |
| Valid from | Tue, 09 Apr 2024 04:05:05 UTC |
| Valid until | Sat, 17 May 2025 16:05:51 UTC (expires in 1 year) |
| Key | RSA 2048 bits(e 65537) |
| Weak key (Debian) | No |
| Issuer | IDFCBANKCA AIA: ldap:///CN=IDFCBANKCA,CN=AIA,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=IDFCBANK,DC=COM?cACertificate?base?objectClass=certificationAuthority |
| Signature algorithm | SHA256withRSA |
| Extended Validation | No |
| Certificate Transparency | No |
| OCSP Must Staple | No |
| Revocation information | None |
| DNS CAA | No (more info) |
| Trusted | No NOT TRUSTED (Why?) Mozilla Apple Android Java Windows |
| Additional Certificates (if supplied) | |
| Certificates provided | 1 (1420 bytes) |
| Chain issues | Incomplete |
  Certification Paths |
| No trust paths available Issuer unknown, or intermediate certificate(s) missing. | ||
| No trust paths available Issuer unknown, or intermediate certificate(s) missing. | ||
| No trust paths available Issuer unknown, or intermediate certificate(s) missing. | ||
| No trust paths available Issuer unknown, or intermediate certificate(s) missing. | ||
| No trust paths available Issuer unknown, or intermediate certificate(s) missing. |
Click here to expand
Configuration
| Protocols | |
| TLS 1.3 | Yes |
| TLS 1.2 | Yes |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | No |
| Cipher Suites | ||
| # TLS 1.3 (suites in server-preferred order) | ||
TLS_AES_256_GCM_SHA384 (0x1302) ECDH x25519 (eq. 3072 bits RSA) FS | 256 | |
TLS_CHACHA20_POLY1305_SHA256 (0x1303) ECDH x25519 (eq. 3072 bits RSA) FS | 256 | |
TLS_AES_128_GCM_SHA256 (0x1301) ECDH x25519 (eq. 3072 bits RSA) FS | 128 | |
| # TLS 1.2 (suites in server-preferred order) | ||
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) ECDH x25519 (eq. 3072 bits RSA) FS | 256 | |
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8) ECDH x25519 (eq. 3072 bits RSA) FS | 256 | |
TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 (0xc061) ECDH x25519 (eq. 3072 bits RSA) FS | 256 | |
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) ECDH x25519 (eq. 3072 bits RSA) FS | 128 | |
TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 (0xc060) ECDH x25519 (eq. 3072 bits RSA) FS | 128 | |
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH x25519 (eq. 3072 bits RSA) FS WEAK | 256 | |
TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384 (0xc077) ECDH x25519 (eq. 3072 bits RSA) FS WEAK | 256 | |
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH x25519 (eq. 3072 bits RSA) FS WEAK | 128 | |
TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 (0xc076) ECDH x25519 (eq. 3072 bits RSA) FS WEAK | 128 | |
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH x25519 (eq. 3072 bits RSA) FS WEAK | 256 | |
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH x25519 (eq. 3072 bits RSA) FS WEAK | 128 | |
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d) WEAK | 256 | |
TLS_RSA_WITH_AES_256_CCM_8 (0xc0a1) WEAK | 256 | |
TLS_RSA_WITH_AES_256_CCM (0xc09d) WEAK | 256 | |
TLS_RSA_WITH_ARIA_256_GCM_SHA384 (0xc051) WEAK | 256 | |
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c) WEAK | 128 | |
TLS_RSA_WITH_AES_128_CCM_8 (0xc0a0) WEAK | 128 | |
TLS_RSA_WITH_AES_128_CCM (0xc09c) WEAK | 128 | |
TLS_RSA_WITH_ARIA_128_GCM_SHA256 (0xc050) WEAK | 128 | |
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d) WEAK | 256 | |
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 (0xc0) WEAK | 256 | |
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c) WEAK | 128 | |
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 (0xba) WEAK | 128 | |
TLS_RSA_WITH_AES_256_CBC_SHA (0x35) WEAK | 256 | |
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84) WEAK | 256 | |
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) WEAK | 128 | |
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x41) WEAK | 128 | |
| Handshake Simulation | |||
| Android 4.4.2 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Android 5.0.0 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
| Android 6.0 | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
| Android 7.0 | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| Android 8.0 | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| Android 8.1 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| Android 9.0 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| BingPreview Jan 2015 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Chrome 49 / XP SP3 | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Chrome 69 / Win 7R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| Chrome 70 / Win 10 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| Chrome 80 / Win 10R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| Firefox 31.3.0 ESR / Win 7 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
| Firefox 47 / Win 7R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Firefox 49 / XP SP3 | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Firefox 62 / Win 7R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| Firefox 73 / Win 10R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| Googlebot Feb 2018 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| IE 11 / Win 7R | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| IE 11 / Win 8.1R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| IE 11 / Win Phone 8.1R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 ECDH secp256r1 FS |
| IE 11 / Win Phone 8.1 UpdateR | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| IE 11 / Win 10R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Edge 15 / Win 10R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| Edge 16 / Win 10R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| Edge 18 / Win 10R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| Edge 13 / Win Phone 10R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Java 8u161 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Java 11.0.3 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Java 12.0.1 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| OpenSSL 1.0.1lR | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| OpenSSL 1.0.2sR | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| OpenSSL 1.1.0kR | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
| OpenSSL 1.1.1cR | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| Safari 6 / iOS 6.0.1 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| Safari 7 / iOS 7.1R | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| Safari 7 / OS X 10.9R | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| Safari 8 / iOS 8.4R | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| Safari 8 / OS X 10.10R | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS |
| Safari 9 / iOS 9R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Safari 9 / OS X 10.11R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Safari 10 / iOS 10R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Safari 10 / OS X 10.12R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Safari 12.1.2 / MacOS 10.14.6 BetaR | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| Safari 12.1.1 / iOS 12.3.1R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
| Apple ATS 9 / iOS 9R | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Yahoo Slurp Jan 2015 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| YandexBot Jan 2015 | RSA 2048 (SHA256) | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| # Not simulated clients (Protocol mismatch) | |||
| Android 2.3.7 No SNI 2 | Protocol mismatch (not simulated) | ||
| Android 4.0.4 | Protocol mismatch (not simulated) | ||
| Android 4.1.1 | Protocol mismatch (not simulated) | ||
| Android 4.2.2 | Protocol mismatch (not simulated) | ||
| Android 4.3 | Protocol mismatch (not simulated) | ||
| Baidu Jan 2015 | Protocol mismatch (not simulated) | ||
| IE 6 / XP No FS 1 No SNI 2 | Protocol mismatch (not simulated) | ||
| IE 7 / Vista | Protocol mismatch (not simulated) | ||
| IE 8 / XP No FS 1 No SNI 2 | Protocol mismatch (not simulated) | ||
| IE 8-10 / Win 7R | Protocol mismatch (not simulated) | ||
| IE 10 / Win Phone 8.0 | Protocol mismatch (not simulated) | ||
| Java 6u45 No SNI 2 | Protocol mismatch (not simulated) | ||
| Java 7u25 | Protocol mismatch (not simulated) | ||
| OpenSSL 0.9.8y | Protocol mismatch (not simulated) | ||
| Safari 5.1.9 / OS X 10.6.8 | Protocol mismatch (not simulated) | ||
| Safari 6.0.4 / OS X 10.8.4R | Protocol mismatch (not simulated) | ||
| Click here to expand | |||
| (1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it. | |||
| (2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI. | |||
| (3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version. | |||
| (R) Denotes a reference browser or client, with which we expect better effective security. | |||
| (All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE). | |||
| (All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake. | |||
| Protocol Details | |
| Secure Renegotiation | Supported |
| Secure Client-Initiated Renegotiation | No |
| Insecure Client-Initiated Renegotiation | No |
| BEAST attack | Mitigated server-side (more info) |
| POODLE (SSLv3) | No, SSL 3 not supported (more info) |
| POODLE (TLS) | No (more info) |
| Zombie POODLE | Unknown (more info) |
| GOLDENDOODLE | Unknown (more info) |
| OpenSSL 0-Length | Unknown (more info) |
| Sleeping POODLE | Unknown (more info) |
| Downgrade attack prevention | Yes, TLS_FALLBACK_SCSV supported (more info) |
| SSL/TLS compression | No |
| RC4 | No |
| Heartbeat (extension) | No |
| Heartbleed (vulnerability) | No (more info) |
| Ticketbleed (vulnerability) | No (more info) |
| OpenSSL CCS vuln. (CVE-2014-0224) | No (more info) |
| OpenSSL Padding Oracle vuln. (CVE-2016-2107) | No (more info) |
| ROBOT (vulnerability) | No (more info) |
| Forward Secrecy | Yes (with most browsers) ROBUST (more info) |
| ALPN | Yes http/1.1 |
| NPN | Yes http/1.1 |
| Session resumption (caching) | No (IDs assigned but not accepted) |
| Session resumption (tickets) | Yes |
| OCSP stapling | No |
| Strict Transport Security (HSTS) | No |
| HSTS Preloading | Not in: Chrome Edge Firefox IE |
| Public Key Pinning (HPKP) | No (more info) |
| Public Key Pinning Report-Only | No |
| Public Key Pinning (Static) | No (more info) |
| Long handshake intolerance | No |
| TLS extension intolerance | No |
| TLS version intolerance | No |
| Incorrect SNI alerts | No |
| Uses common DH primes | No, DHE suites not supported |
| DH public server param (Ys) reuse | No, DHE suites not supported |
| ECDH public server param reuse | No |
| Supported Named Groups | x25519, secp256r1, x448, secp521r1, secp384r1 (server preferred order) |
| SSL 2 handshake compatibility | No |
| 0-RTT enabled | No |
| HTTP Requests |
| 1https://imformuat.idfcfirstbank.com/ (HTTP/1.1 200 OK) | 1 | |
| Server | nginx/1.18.0 (Ubuntu) | |
| Date | Wed, 24 Apr 2024 04:55:18 GMT | |
| Content-Type | text/html; charset=utf-8 | |
| Content-Length | 1577 | |
| Connection | close | |
| X-Powered-By | Express | |
| Access-Control-Allow-Origin | * | |
| Access-Control-Allow-Methods | * | |
| Access-Control-Allow-Headers | * | |
| Accept-Ranges | bytes | |
| ETag | W/"629-nBkOQ00Hqp8NlSDtyGZkQckzW9Q" | |
| Vary | Accept-Encoding | |
| Miscellaneous | |
| Test date | Wed, 24 Apr 2024 04:55:04 UTC |
| Test duration | 175.414 seconds |
| HTTP status code | 200 |
| HTTP server signature | nginx/1.18.0 (Ubuntu) |
| Server hostname | - |
Why is my certificate not trusted?
There are many reasons why a certificate may not be trusted. Theexact problem is indicated on the report card in bright red.The problems fall into three categories:
- Invalid certificate
- Invalid configuration
- Unknown Certificate Authority
1. Invalid certificate
A certificate is invalid if:
- It is used before its activation date
- It is used after its expiry date
- Certificate hostnames don't match the site hostname
- It has been revoked
- It has insecure signature
- It has been blacklisted
2. Invalid configuration
In some cases, the certificate chain does notcontain all the necessary certificates to connect the webserver certificate to one of the root certificates in our trust store.Less commonly, one of the certificates in the chain (other than theweb server certificate) will have expired, and that invalidates theentire chain.
3. Unknown Certificate Authority
In order for trust to be established, we must have the root certificateof the signing Certificate Authority in our trust store. SSL Labs does notmaintain its own trust store; instead we use the store maintained by Mozilla.
If we mark a web site as not trusted, that means that the average web user'sbrowser will not trust it either. For certain special groups of users, suchweb sites can still be secure. For example, if you can securely verify thata self-signed web site is operated by a person you trust, then you can trustthat self-signed web site too. Or, if you work for an organisation that managesits own trust, and you have their own root certificate already embedded inyour browser. Such special cases do not work for the general public, however,and this is what we indicate on our report card.
4. Interoperability issues
In some rare cases trust cannot be established because of interoperabilityissues between our code and the code or configuration running on the server.We manually review such cases, but if you encounter such an issue please feelfree to contact us. Such problems are very difficult to troubleshoot and youmay be able to provide us with information that might help us determine theroot cause.
SSL Report v2.3.0
