SSL-Tools

SSL check results of lugibello.ch

NEW You can also bulk check multiple servers.

Discover if the mail servers for lugibello.ch can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Wed, 12 Feb 2025 20:50:45 +0000

We can not guarantee a secure connection to the mailservers of lugibello.ch!

Please contact the operator of lugibello.ch and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/lugibello.ch

Servers

Incoming Mails

These servers are responsible for incoming mails to @lugibello.ch addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.lugibello.ch
2001:8e0:151a::20c:29ff:fe7a:abdd
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.lugibello.ch
87.239.206.238
 10
supported
mail.lugibello.ch
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
12 s

Outgoing Mails

We have not received any emails from a @lugibello.ch address so far. Test mail delivery

Certificates

First seen at:

CN=mail.lugibello.ch

Certificate chain
  • mail.lugibello.ch
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.lugibello.ch
Alternative Names
  • mail.lugibello.ch
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-02-12
Not valid after
2025-05-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A8:88:B2:5D:02:F8:0D:6F:EC:F0:84:81:4D:8B:6C:01:31:AF:73:1E:94:70:AE:CD:7F:52:4C:31:29:BE:8F:0C
SHA1
5F:7F:6F:23:6A:ED:7F:6A:EC:0E:37:42:40:77:5E:4A:46:AA:0B:DB
X509v3 extensions
subjectKeyIdentifier
  • 07:01:9B:4B:6D:0E:9A:42:29:93:4C:E1:B9:6F:F2:07:E7:72:CE:7A
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Feb 12 12:13:23.920 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A2:A3:74:10:A0:EB:D5:ED:28:99:78:
  • C9:48:E4:B5:0E:47:17:17:73:10:82:4B:78:D0:6B:F1:
  • F5:2F:13:2A:B8:02:21:00:90:CA:5A:95:6B:D8:7D:97:
  • 84:A7:3F:A7:1E:E0:89:54:32:14:2E:AD:E6:D0:24:A2:
  • 2B:80:DD:D7:55:1C:80:FD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Feb 12 12:13:23.912 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:64:5C:61:24:68:7A:37:5D:5C:47:2A:B9:
  • E7:16:CF:13:72:4E:4F:5E:AE:09:68:1C:24:2F:D7:2D:
  • 36:D3:AC:40:02:21:00:AD:B9:15:48:DB:FA:FD:3D:87:
  • EE:18:F8:B0:0E:D9:C3:CA:B3:28:C7:75:C3:8F:9B:CA:
  • 52:8F:10:FA:D1:19:D0