SSL check results of noelting-gebrueder.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for noelting-gebrueder.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 Fri, 30 Apr 2021 10:21:09 +0000

The mailservers of noelting-gebrueder.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @noelting-gebrueder.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail2.noelting-gebrueder.de
195.80.216.210
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.noelting-gebrueder.de
89.163.229.8
20
supported
mail.noelting-gebrueder.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.noelting-gebrueder.de

Certificate chain
  • mail.noelting-gebrueder.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • mail.noelting-gebrueder.de
Alternative Names
  • mail.noelting-gebrueder.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-12
Not valid after
2021-06-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CC:5E:50:05:64:5D:52:13:D4:6D:2E:F4:D0:80:FA:A8:7B:9D:E1:49:DF:CC:11:C6:02:43:F2:5C:2C:B8:5A:76
SHA1
C0:01:D4:CE:99:46:6E:D7:3E:91:14:45:35:5A:96:93:9D:62:E6:18
X509v3 extensions
subjectKeyIdentifier
  • 4D:50:80:1B:80:FB:F1:5E:CE:AD:FD:45:64:3F:3F:55:AF:5B:9A:D2
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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Mar 12 16:42:36.345 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:86:3E:BC:3C:EA:36:7E:E5:7C:A0:03:
  • 9E:43:48:A7:CB:C5:ED:43:3B:20:83:56:75:34:99:F3:
  • D6:A9:05:85:84:02:20:0A:A4:8F:DD:F9:DC:71:FC:4B:
  • D2:C8:51:05:6F:87:60:6D:A4:88:A0:52:11:CC:0A:3B:
  • C4:1F:E8:3F:7D:F0:D8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Mar 12 16:42:36.335 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6D:D3:DE:36:30:9D:BE:93:7D:12:76:D1:
  • A8:ED:29:99:D0:D5:C4:93:73:49:1B:E2:79:02:D3:A8:
  • 3C:AB:44:B7:02:20:12:12:30:AA:03:D6:93:69:31:59:
  • E5:AF:F7:C4:DC:FB:CE:B9:5D:30:9F:1E:93:6F:F6:58:
  • B3:31:4A:42:02:57