SSL-Tools

SSL check results of riegger.it

NEW You can also bulk check multiple servers.

Discover if the mail servers for riegger.it 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 Fri, 26 Apr 2024 20:01:54 +0000

The mailservers of riegger.it can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @riegger.it addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.riegger.it
2a01:4f8:1c0c:4d59::1
 10
supported
mail.riegger.it
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.riegger.it
91.107.225.244
 10
supported
mail.riegger.it
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.riegger.it

Certificate chain
  • mail.riegger.it
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.riegger.it
Alternative Names
  • autoconfig.bennyriegger.de
  • autodiscover.bennyriegger.de
  • autodiscover.riegger.it
  • mail.riegger.it
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-20
Not valid after
2024-07-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4B:9F:43:90:45:E4:CB:4E:AB:68:E1:75:12:7B:07:E5:B7:C8:CC:F3:2A:9C:96:8C:28:14:0D:36:A4:56:AC:27
SHA1
A7:87:9F:8E:09:40:84:1A:D9:95:98:D9:B7:A9:78:46:4E:2F:97:4B
X509v3 extensions
subjectKeyIdentifier
  • 53:09:9E:ED:97:9A:B8:78:55:2E:10:10:D6:26:2C:F8:8C:67:F8:D6
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 : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 20 23:55:13.059 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:45:8D:00:DB:F2:15:B5:50:7D:39:EC:0A:
  • 7C:7B:FF:1E:61:3B:A0:5F:35:79:50:E5:CD:85:BE:C0:
  • 2F:3C:53:33:02:21:00:AA:5C:DC:6E:6F:32:FF:AC:D0:
  • 27:DF:6C:A4:C0:CC:3F:77:64:19:FE:17:D2:51:34:EB:
  • 1D:5B:F9:52:75:E6:56
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 20 23:55:13.201 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B6:90:9A:E9:6C:E1:E5:8F:CE:EF:83:
  • 5A:B9:95:14:2E:49:F7:97:A3:9F:71:A2:F3:AE:64:93:
  • 5C:22:F3:2E:C8:02:20:23:63:52:C2:64:D2:D2:0A:64:
  • 62:76:F0:84:49:99:E8:DE:B3:37:CB:20:02:3B:6E:A5:
  • 54:48:42:80:7F:7D:A5