SSL Report:
netbox.mlsys.network
(217.195.7.180)
Assessed on: Thu, 07 Aug 2025 22:09:08 UTC
| Clear cache
Summary
If trust issues are ignored: A
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's certificate chain is incomplete. Grade capped to B.
This site works only in browsers with SNI support.
This server supports TLS 1.3. MORE INFO »
Certificate #1: EC 256 bits (SHA256withECDSA)
|
Server Key and Certificate #1
|
|
| Subject |
mlconsult.com
Fingerprint SHA256: 5a8d6b317273a4e9c879981aeb7a92871213f643285018fa700849db2d247a55 Pin SHA256: 3XhG+doMkSf2UTPMijlB84MkBc+aGxqgAcMqyGycGRs= |
| Common names | mlconsult.com |
| Alternative names | mlconsult.com sohoml-lab.mlconsult.com sophia.mlconsult.com vf-apm-lab.mlconsult.com vf-apm.mlconsult.com vf-bc-lab.mlconsult.com vf-bc.mlconsult.com vf-sso-lab.mlconsult.com vf-sso.mlconsult.com inhv.mlconsult.com inhv-lab.mlconsult.com imc-lab.mlconsult.com imc.mlconsult.com vf-rfc.mlconsult.com vf-rfc-lab.mlconsult.com ritarms-lab.mlconsult.com ritarms.mlconsult.com MISMATCH |
| Serial Number | 044cfa787a76fd302c8bc4b59c2eee77 |
| Valid from | Thu, 07 Aug 2025 00:00:00 UTC |
| Valid until | Wed, 26 Aug 2026 23:59:59 UTC (expires in 1 year) |
| Key | EC 256 bits |
| Weak key (Debian) | No |
| Issuer | GeoTrust TLS ECC CA G1
AIA: http://cacerts.geotrust.com/GeoTrustTLSECCCAG1.crt |
| Signature algorithm | SHA256withECDSA |
| Extended Validation | No |
| Certificate Transparency | Yes (certificate) |
| OCSP Must Staple | No |
| Revocation information |
CRL, OCSP CRL: http://cdp.geotrust.com/GeoTrustTLSECCCAG1.crl OCSP: http://status.geotrust.com |
| Revocation status | Good (not revoked) |
| DNS CAA | No (more info) |
| Trusted | No NOT TRUSTED
(Why?)
Mozilla Apple Android Java Windows |
|
Additional Certificates (if supplied)
|
|
| Certificates provided | 1 (1551 bytes) |
| Chain issues | Incomplete |
Certification Paths |
Configuration
| Protocols | |
| TLS 1.3 | Yes |
| TLS 1.2 | No |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | No |
| Cipher Suites | ||
|
# TLS 1.3 (we could not determine if the server has a preference)
|
||
TLS_AES_128_GCM_SHA256 (0x1301)
ECDH secp256r1 (eq. 3072 bits RSA) FS
|
128 | |
TLS_CHACHA20_POLY1305_SHA256 (0x1303)
ECDH secp256r1 (eq. 3072 bits RSA) FS
|
256 | |
| Handshake Simulation | |||
| Android 8.1 | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Android 9.0 | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Chrome 69 / Win 7 R |
Server closed connection |
||
| Chrome 70 / Win 10 | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Chrome 80 / Win 10 R | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Firefox 62 / Win 7 R |
Server closed connection |
||
| Firefox 73 / Win 10 R | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Java 11.0.3 | - | TLS 1.3 | TLS_AES_128_GCM_SHA256 ECDH secp256r1 FS |
| Java 12.0.1 | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| OpenSSL 1.1.0k R |
Server closed connection |
||
| OpenSSL 1.1.1c R | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Safari 12.1.2 / MacOS 10.14.6 Beta R | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH secp256r1 FS |
| Safari 12.1.1 / iOS 12.3.1 R | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 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) |
||
| 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) |
||
| Baidu Jan 2015 |
Protocol mismatch (not simulated) |
||
| BingPreview Jan 2015 |
Protocol mismatch (not simulated) |
||
| Chrome 49 / XP SP3 |
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) |
||
| Googlebot Feb 2018 |
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 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 6u45 No SNI 2 |
Protocol mismatch (not simulated) |
||
| Java 7u25 |
Protocol mismatch (not simulated) |
||
| Java 8u161 |
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) |
||
| 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) |
||
| 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 | |
| ROBOT (vulnerability) | No (more info) |
| Forward Secrecy | Yes (with most browsers) ROBUST (more info) |
| ALPN | Yes h2 http/1.1 |
| 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) |
| Supported Named Groups | secp256r1 |
| SSL 2 handshake compatibility | No |
| 0-RTT enabled | No |
|
HTTP Requests
|
|
1 https://netbox.mlsys.network/
(HTTP/1.1 302 Found)
| 1 | |
| Server | nginx/1.24.0 (Ubuntu) | |
| Date | Thu, 07 Aug 2025 22:08:47 GMT | |
| Content-Type | text/html; charset=utf-8 | |
| Content-Length | 0 | |
| Connection | close | |
| Location | /login/?next=/ | |
| X-Request-ID | 657efdac-9e85-4563-9239-4f36ea4d2c6c | |
| Vary | HX-Request, Accept-Language, Cookie, origin | |
| X-Content-Type-Options | nosniff | |
| Referrer-Policy | same-origin | |
| Cross-Origin-Opener-Policy | same-origin | |
| X-Frame-Options | SAMEORIGIN | |
| Content-Language | en | |
|
2 https://netbox.mlsys.network/login/?next=/
(HTTP/1.1 302 Found)
| 2 | |
| Server | nginx/1.24.0 (Ubuntu) | |
| Date | Thu, 07 Aug 2025 22:08:48 GMT | |
| Content-Type | text/html; charset=utf-8 | |
| Content-Length | 0 | |
| Connection | close | |
| Location | /plugins/otp/ | |
| X-Request-ID | 4780a0e3-a36b-4669-aaeb-2025e0d0775f | |
| Vary | HX-Request, Accept-Language, Cookie, origin | |
| X-Content-Type-Options | nosniff | |
| Referrer-Policy | same-origin | |
| Cross-Origin-Opener-Policy | same-origin | |
| X-Frame-Options | SAMEORIGIN | |
| Content-Language | en | |
|
3 https://netbox.mlsys.network/plugins/otp/
(HTTP/1.1 200 OK)
| 3 | |
| Server | nginx/1.24.0 (Ubuntu) | |
| Date | Thu, 07 Aug 2025 22:08:49 GMT | |
| Content-Type | text/html; charset=utf-8 | |
| Content-Length | 3526 | |
| Connection | close | |
| Expires | Thu, 07 Aug 2025 22:08:49 GMT | |
| Cache-Control | max-age=0, no-cache, no-store, must-revalidate, private | |
| Vary | HX-Request, Accept-Language, Cookie, origin | |
| X-Request-ID | 6ac585a8-b589-4e42-9658-8032454c3a7a | |
| X-Content-Type-Options | nosniff | |
| Referrer-Policy | same-origin | |
| Cross-Origin-Opener-Policy | same-origin | |
| X-Frame-Options | SAMEORIGIN | |
| Content-Language | en | |
| Set-Cookie | csrftoken=LbTFr57iInuIjx7H7wprWylNuX4Y1ech; expires=Thu, 06 Aug 2026 22:08:49 GMT; Max-Age=31449600; Path=/; SameSite=Lax | |
| Miscellaneous | |
| Test date | Thu, 07 Aug 2025 22:08:39 UTC |
| Test duration | 28.928 seconds |
| HTTP status code | 200 |
| HTTP server signature | nginx/1.24.0 (Ubuntu) |
| 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