SSL Report:
remote.inpaq.fr
(92.175.29.234)
Assessed on: Mon, 22 Sep 2025 20:49:05 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 uses only RC4 suites, which are insecure. Modern browsers won't connect to it.
This server's certificate is not trusted, see below for details.
This server's certificate is not trusted by major browsers. MORE INFO »
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's certificate chain is incomplete. Grade capped to B.
HTTP request to this server failed, see below for details.
This server does not support TLS 1.3. MORE INFO »
Certificate #1: RSA 2048 bits (SHA1withRSA)
|
Server Key and Certificate #1
|
|
| Subject |
remote.inpaq.fr
Fingerprint SHA256: 216e43bf18ced2ab01f568ebdee7d707e63d065d3fcd5da768f9b80fbe6a1b8b Pin SHA256: iGLhQ2g6HN5VhSVLszT7CwYuaZPQq8UhNoXgBvn3S18= |
| Common names | remote.inpaq.fr |
| Alternative names | remote.inpaq.fr vmsrv-mail01.inpaq.arzacq autodiscover.INPAQ.ARZACQ autodiscover.inpaq.fr autodiscover.jambon-de-bayonne.fr autodiscover.pyragena.fr |
| Serial Number | 60da3c6100000000004a |
| Valid from | Tue, 04 Feb 2025 11:59:47 UTC |
| Valid until | Thu, 04 Feb 2027 11:59:47 UTC (expires in 1 year and 4 months) |
| Key | RSA 2048 bits (e 65537) |
| Weak key (Debian) | No |
| Issuer | INPAQ-VMSRV-AD01-CA
AIA: ldap:///CN=INPAQ-VMSRV-AD01-CA,CN=AIA,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=INPAQ,DC=ARZACQ?cACertificate?base?objectClass=certificationAuthority |
| Signature algorithm | SHA1withRSA INSECURE |
| 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 (1572 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. |
Configuration
| Protocols | |
| TLS 1.3 | No |
| TLS 1.2 | No |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | YesD |
| (D) Protocol is supported, but with all cipher suites disabled | |
| Cipher Suites | ||
|
# SSL 2 (client selects suite)
|
||
SSL_CK_RC4_128_WITH_MD5 (0x10080)
INSECURE
|
128 | |
SSL_CK_DES_192_EDE3_CBC_WITH_MD5 (0x700c0)
INSECURE
|
112 | |
| Handshake Simulation | |||
| IE 6 / XP No FS 1 No SNI 2 |
Server closed connection |
||
| Java 6u45 No SNI 2 |
Server closed connection |
||
|
# 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) |
||
| Android 4.4.2 |
Protocol mismatch (not simulated) |
||
| Android 5.0.0 |
Protocol mismatch (not simulated) |
||
| 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) |
||
| Baidu Jan 2015 |
Protocol mismatch (not simulated) |
||
| BingPreview Jan 2015 |
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) |
||
| Googlebot Feb 2018 |
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 7 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 10 / Win Phone 8.0 |
Protocol mismatch (not simulated) |
||
| IE 11 / Win Phone 8.1 R |
Protocol mismatch (not simulated) |
||
| IE 11 / Win Phone 8.1 Update 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 7u25 |
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) |
||
| OpenSSL 0.9.8y |
Protocol mismatch (not simulated) |
||
| OpenSSL 1.0.1l R |
Protocol mismatch (not simulated) |
||
| OpenSSL 1.0.2s R |
Protocol mismatch (not simulated) |
||
| OpenSSL 1.1.0k R |
Protocol mismatch (not simulated) |
||
| OpenSSL 1.1.1c R |
Protocol mismatch (not simulated) |
||
| Safari 5.1.9 / OS X 10.6.8 |
Protocol mismatch (not simulated) |
||
| Safari 6 / iOS 6.0.1 |
Protocol mismatch (not simulated) |
||
| Safari 6.0.4 / OS X 10.8.4 R |
Protocol mismatch (not simulated) |
||
| Safari 7 / iOS 7.1 R |
Protocol mismatch (not simulated) |
||
| Safari 7 / OS X 10.9 R |
Protocol mismatch (not simulated) |
||
| Safari 8 / iOS 8.4 R |
Protocol mismatch (not simulated) |
||
| Safari 8 / OS X 10.10 R |
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) |
||
| Yahoo Slurp Jan 2015 |
Protocol mismatch (not simulated) |
||
| YandexBot Jan 2015 |
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 | |
| Renegotiation | No (only SSL 2.0 supported) |
| BEAST attack | Not mitigated server-side (more info) |
| POODLE (SSLv3) | No, SSL 3 not supported (more info) |
| POODLE (TLS) | (more info) |
| Zombie POODLE | No (more info) |
| GOLDENDOODLE | No (more info) |
| OpenSSL 0-Length | No (more info) |
| Sleeping POODLE | No (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) | Unknown (more info) |
| OpenSSL CCS vuln. (CVE-2014-0224) | Unknown (more info) |
| OpenSSL Padding Oracle vuln. (CVE-2016-2107) |
Unknown (more info) |
| ROBOT (vulnerability) | Unknown (more info) |
| Forward Secrecy | No WEAK (more info) |
| ALPN | No |
| NPN | No |
| Session resumption (tickets) | No |
| OCSP stapling | No |
| Strict Transport Security (HSTS) | Unknown (failed HTTP request?) |
| HSTS Preloading | |
| Public Key Pinning (HPKP) | Unknown (failed HTTP request?) |
| Public Key Pinning Report-Only | Unknown (failed HTTP request?) |
| Public Key Pinning (Static) | Unknown |
| Long handshake intolerance | No |
| TLS extension intolerance | Not applicable (only SSL 2.0 supported) |
| TLS version intolerance | Not applicable (only SSL 2.0 supported) |
| 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://remote.inpaq.fr/
(Request failed)
|
| Miscellaneous | |
| Test date | Mon, 22 Sep 2025 20:48:55 UTC |
| Test duration | 9.712 seconds |
| HTTP status code | Request failed |
| HTTP server signature | Unknown |
| Server hostname | - |
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