SSL Report:
api.srfcconnect.in
(115.124.125.151)
Assessed on: Fri, 29 Aug 2025 04:29:31 UTC
| Clear cache
Summary
0
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 supports only SSL 3 as its best protocol. Grade set to F.
MORE INFO »
This site is intolerant to newer protocol versions, which might cause connection failures.
The server supports only older protocols, but not the current best TLS 1.2 or TLS 1.3. Grade capped to C.
MORE INFO »
This server does not support Forward Secrecy with the reference browsers.
Grade capped to B.
MORE INFO »
This server does not support Authenticated encryption (AEAD) cipher suites. Grade capped to B.
MORE INFO »
This server does not support TLS 1.3. MORE INFO »
Certificate #1: RSA 2048 bits (SHA256withRSA)
|
Server Key and Certificate #1
|
|
| Subject |
multifysolutions.com
Fingerprint SHA256: 460404b5ab39d75c069f44dc468c1963dd60db0d82a1c94fbeabf04b1f73630e Pin SHA256: wPY6QF5gec4lzJ2KPKS/wSlMh0euu9bfCdLoFGpan9g= |
| Common names | multifysolutions.com |
| Alternative names | multifysolutions.com MISMATCH |
| Serial Number | 0643706cd2593c59c6d5235551f9079322a2 |
| Valid from | Tue, 15 Jul 2025 05:37:23 UTC |
| Valid until | Mon, 13 Oct 2025 05:37:22 UTC (expires in 1 month and 13 days) |
| Key | RSA 2048 bits (e 65537) |
| Weak key (Debian) | No |
| Issuer | R10
AIA: http://r10.i.lencr.org/ |
| Signature algorithm | SHA256withRSA |
| Extended Validation | No |
| Certificate Transparency | Yes (certificate) |
| OCSP Must Staple | No |
| Revocation information |
CRL CRL: http://r10.c.lencr.org/35.crl |
| Revocation status | Validation error
CRL ERROR: IOException occurred |
| DNS CAA | No (more info) |
| Trusted | No NOT TRUSTED
(Why?)
Mozilla Apple Android Java Windows |
Certification Paths |
Configuration
| Protocols | |
| TLS 1.3 | No |
| TLS 1.2 | No |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 INSECURE | Yes |
| SSL 2 | No |
| Cipher Suites | ||
|
# SSL 3 (we could not determine if the server has a preference)
|
||
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)
WEAK
|
112 | |
|
# TLS 1.0 No SNI (suites in server-preferred order)
|
||
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
ECDH secp384r1 (eq. 7680 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_CBC_SHA (0x35)
WEAK
|
256 | |
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)
WEAK
|
128 | |
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)
WEAK
|
112 | |
| Handshake Simulation | |||
| Android 2.3.7 No SNI 2 | RSA 2048 (SHA256) | TLS 1.0 | TLS_RSA_WITH_AES_128_CBC_SHA No FS |
| Android 4.0.4 |
Server closed connection |
||
| Android 4.1.1 |
Server closed connection |
||
| Android 4.2.2 |
Server closed connection |
||
| Android 4.3 |
Server closed connection |
||
| Android 4.4.2 |
Server closed connection |
||
| Android 5.0.0 |
Server closed connection |
||
| Baidu Jan 2015 |
Server closed connection |
||
| BingPreview Jan 2015 |
Server closed connection |
||
| Googlebot Feb 2018 |
Server closed connection |
||
| IE 6 / XP No FS 1 No SNI 2 | RSA 2048 (SHA256) | SSL 3 | TLS_RSA_WITH_3DES_EDE_CBC_SHA |
| IE 7 / Vista |
Server closed connection |
||
| IE 8 / XP No FS 1 No SNI 2 | RSA 2048 (SHA256) | TLS 1.0 | TLS_RSA_WITH_3DES_EDE_CBC_SHA |
| IE 8-10 / Win 7 R |
Server closed connection |
||
| IE 10 / Win Phone 8.0 |
Server closed connection |
||
| IE 11 / Win Phone 8.1 R |
Server closed connection |
||
| IE 11 / Win Phone 8.1 Update R |
Server closed connection |
||
| Java 6u45 No SNI 2 | RSA 2048 (SHA256) | TLS 1.0 | TLS_RSA_WITH_AES_128_CBC_SHA No FS |
| Java 7u25 |
Server closed connection |
||
| OpenSSL 0.9.8y |
Server closed connection |
||
| OpenSSL 1.0.1l R |
Server closed connection |
||
| OpenSSL 1.0.2s R |
Server closed connection |
||
| OpenSSL 1.1.0k R |
Server closed connection |
||
| OpenSSL 1.1.1c R |
Server closed connection |
||
| Safari 5.1.9 / OS X 10.6.8 |
Server closed connection |
||
| Safari 6 / iOS 6.0.1 |
Server closed connection |
||
| Safari 6.0.4 / OS X 10.8.4 R |
Server closed connection |
||
| Safari 7 / iOS 7.1 R |
Server closed connection |
||
| Safari 7 / OS X 10.9 R |
Server closed connection |
||
| Safari 8 / iOS 8.4 R |
Server closed connection |
||
| Safari 8 / OS X 10.10 R |
Server closed connection |
||
| Yahoo Slurp Jan 2015 |
Server closed connection |
||
| YandexBot Jan 2015 |
Server closed connection |
||
|
# Not simulated clients (Protocol mismatch)
|
|||
| Android 6.0 |
Protocol mismatch (not simulated) |
||
| Android 7.0 |
Protocol mismatch (not simulated) |
||
| Android 8.0 |
Protocol mismatch (not simulated) |
||
| Android 8.1 |
Protocol mismatch (not simulated) |
||
| Android 9.0 |
Protocol mismatch (not simulated) |
||
| Chrome 49 / XP SP3 |
Protocol mismatch (not simulated) |
||
| Chrome 69 / Win 7 R |
Protocol mismatch (not simulated) |
||
| Chrome 70 / Win 10 |
Protocol mismatch (not simulated) |
||
| Chrome 80 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Firefox 31.3.0 ESR / Win 7 |
Protocol mismatch (not simulated) |
||
| Firefox 47 / Win 7 R |
Protocol mismatch (not simulated) |
||
| Firefox 49 / XP SP3 |
Protocol mismatch (not simulated) |
||
| Firefox 62 / Win 7 R |
Protocol mismatch (not simulated) |
||
| Firefox 73 / Win 10 R |
Protocol mismatch (not simulated) |
||
| IE 11 / Win 7 R |
Protocol mismatch (not simulated) |
||
| IE 11 / Win 8.1 R |
Protocol mismatch (not simulated) |
||
| IE 11 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 15 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 16 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 18 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 13 / Win Phone 10 R |
Protocol mismatch (not simulated) |
||
| Java 8u161 |
Protocol mismatch (not simulated) |
||
| Java 11.0.3 |
Protocol mismatch (not simulated) |
||
| Java 12.0.1 |
Protocol mismatch (not simulated) |
||
| Safari 9 / iOS 9 R |
Protocol mismatch (not simulated) |
||
| Safari 9 / OS X 10.11 R |
Protocol mismatch (not simulated) |
||
| Safari 10 / iOS 10 R |
Protocol mismatch (not simulated) |
||
| Safari 10 / OS X 10.12 R |
Protocol mismatch (not simulated) |
||
| Safari 12.1.2 / MacOS 10.14.6 Beta R |
Protocol mismatch (not simulated) |
||
| Safari 12.1.1 / iOS 12.3.1 R |
Protocol mismatch (not simulated) |
||
| Apple ATS 9 / iOS 9 R |
Protocol mismatch (not simulated) |
||
| (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 |
Not mitigated server-side (more info)
SSL 3: 0xa
|
| POODLE (SSLv3) |
Vulnerable INSECURE (more info)
SSL 3: 0xa |
| POODLE (TLS) | No, because server doesn't support TLS (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 | Unknown (requires support for at least two protocols, excl. SSL2) |
| 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) | Unknown (more info) |
| OpenSSL Padding Oracle vuln. (CVE-2016-2107) |
No (more info) |
| ROBOT (vulnerability) | No (more info) |
| Forward Secrecy | No WEAK (more info) |
| ALPN | No |
| NPN | No |
| Session resumption (caching) | No (IDs assigned but not accepted) |
| Session resumption (tickets) | No |
| 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 | TLS 1.2 PROBLEMATIC |
| 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, ECDHE suites not supported |
| Supported Named Groups | - |
| SSL 2 handshake compatibility | Yes |
|
HTTP Requests
|
|
1 https://api.srfcconnect.in/
(HTTP/1.1 404 Not Found)
| 1 | |
| Transfer-Encoding | chunked | |
| Server | Microsoft-IIS/10.0 | |
| X-Powered-By | ASP.NET | |
| X-Powered-By-Plesk | PleskWin | |
| Date | Fri, 29 Aug 2025 04:28:27 GMT | |
| Connection | close | |
| Miscellaneous | |
| Test date | Fri, 29 Aug 2025 04:28:11 UTC |
| Test duration | 80.333 seconds |
| HTTP status code | 404 |
| HTTP server signature | Microsoft-IIS/10.0 |
| Server hostname | mail.multifysolutions.com |
Why is my certificate not trusted?
There are many reasons why a certificate may not be trusted. The exact 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 not contain all the necessary certificates to connect the web server certificate to one of the root certificates in our trust store. Less commonly, one of the certificates in the chain (other than the web server certificate) will have expired, and that invalidates the entire chain.
3. Unknown Certificate Authority
In order for trust to be established, we must have the root certificate of the signing Certificate Authority in our trust store. SSL Labs does not maintain 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's browser will not trust it either. For certain special groups of users, such web sites can still be secure. For example, if you can securely verify that a self-signed web site is operated by a person you trust, then you can trust that self-signed web site too. Or, if you work for an organisation that manages its own trust, and you have their own root certificate already embedded in your 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 interoperability issues 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 feel free to contact us. Such problems are very difficult to troubleshoot and you may be able to provide us with information that might help us determine the root cause.
SSL Report v2.4.1