SSL check results of rudloff-online.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for rudloff-online.de 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 Sat, 25 Mar 2023 16:12:40 +0000

The mailservers of rudloff-online.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rudloff-online.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rudloff-online.de
85.239.115.165
10
supported
rudloff-online.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @rudloff-online.de address so far. Test mail delivery

Certificates

First seen at:

CN=rudloff-online.de

Certificate chain
  • rudloff-online.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • rudloff-online.de
Alternative Names
  • autodiscover.rudloff-online.de
  • cloud.rudloff-online.de
  • code.rudloff-online.de
  • git.rudloff-online.de
  • mail.rudloff-online.de
  • portal.rudloff-online.de
  • registry.rudloff-online.de
  • repository.rudloff-online.de
  • rudloff-online.de
  • web.rudloff-online.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-02-03
Not valid after
2023-05-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AA:7B:37:2F:0B:B0:E9:4D:13:50:BC:93:4C:12:84:35:D0:E7:B2:D2:36:CF:61:5C:1A:F7:46:BA:64:25:03:98
SHA1
DD:F0:64:06:72:52:1E:EB:FA:32:A1:DC:D2:24:6E:B9:89:5C:90:67
X509v3 extensions
subjectKeyIdentifier
  • 33:70:00:8D:0A:94:D7:5F:E4:50:B0:50:3D:62:20:CA:09:F0:8A:A7
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Feb 3 02:16:53.441 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:06:69:E2:E2:F1:3A:64:F8:43:01:F5:FC:
  • 84:5F:9F:59:A7:EE:EE:75:55:33:79:60:05:13:11:E6:
  • 03:06:9F:5E:02:21:00:84:B2:82:E1:22:39:26:D1:3C:
  • 21:E8:9E:05:D7:53:82:47:B4:41:0D:F5:5F:B3:75:49:
  • 57:53:D8:9F:1B:52:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Feb 3 02:16:53.466 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7B:51:4D:66:B7:29:15:1D:77:80:42:0C:
  • A0:21:5E:42:4F:20:CD:8F:53:E3:A1:68:C1:D8:8A:E1:
  • E9:87:F3:D7:02:20:18:37:AD:37:20:89:4A:A4:39:95:
  • C4:79:76:33:29:33:4B:46:1A:34:A3:78:CD:A7:FB:A3:
  • 04:14:DA:E2:73:41