SSL check results of kirgus.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for kirgus.net 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

Report created Wed, 20 Dec 2023 14:31:03 +0000

The mailservers of kirgus.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @kirgus.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail04.kirgus.net
2.56.98.121
10
supported
imap.kirgus-it.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
10 s

Outgoing Mails

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

Certificates

First seen at:

CN=imap.kirgus-it.de

Certificate chain
  • imap.kirgus-it.de
    • remaining
    • 384 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • imap.kirgus-it.de
Alternative Names
  • imap.kirgus-it.de
  • imap.kirgus.net
  • mail.kirgus-it.de
  • mail.kirgus.net
  • mail04.kirgus.net
  • smtp.kirgus-it.de
  • smtp.kirgus.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-12-20
Not valid after
2024-03-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A5:3C:EA:C1:55:CB:3D:66:D3:32:80:E6:2D:D9:8B:50:06:A6:6C:27:AC:E4:59:62:3B:EE:F6:62:4B:EA:84:28
SHA1
9F:EA:82:7E:23:93:23:99:A0:F8:66:D3:D3:DE:1A:40:0F:93:D9:A5
X509v3 extensions
subjectKeyIdentifier
  • E2:0E:F7:2D:46:92:08:FD:C6:60:2A:E6:8B:B1:22:6A:F9:7F:AD:CF
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Dec 20 14:11:19.018 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:63:13:DF:AF:F1:46:13:FD:88:3C:47:B6:
  • 1A:D2:2C:EA:13:49:C2:DB:23:D9:83:95:1B:11:FC:36:
  • 60:26:E3:7A:02:21:00:A5:DA:71:4C:E5:E3:16:68:5B:
  • 82:68:F1:92:B4:B4:47:87:64:0D:59:90:17:F3:8B:6F:
  • 5E:84:5C:8A:FF:B1:29
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Dec 20 14:11:19.548 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:97:A7:77:13:10:5A:F8:C8:12:16:09:
  • 01:72:C1:32:BB:1C:E1:52:DE:8B:91:4F:2D:F6:A2:54:
  • 7E:AF:12:02:BE:02:20:49:7E:DB:3C:8A:C1:B9:E4:B6:
  • 77:85:EE:25:0C:7D:19:AE:61:D0:CC:53:11:EE:1E:9A:
  • C0:3B:73:28:91:B5:0F