SSL-Tools

SSL check results of noobynoobsen.de

NEW You can also bulk check multiple servers.

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

JSON Refresh

Report created Fri, 26 Apr 2024 09:41:39 +0000

The mailservers of noobynoobsen.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @noobynoobsen.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
noobynoobsen.de
2a01:488:66:1000:5af:1873::1
 50
supported
noobynoobsen.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
noobynoobsen.de
5.175.24.115
 50
supported
noobynoobsen.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=noobynoobsen.de

Certificate chain
  • noobynoobsen.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)
  • noobynoobsen.de
Alternative Names
  • noobynoobsen.de
  • server1.noobynoobsen.de
  • webadmin.noobynoobsen.de
  • webmail.noobynoobsen.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-10
Not valid after
2024-07-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
97:4F:35:C8:70:1A:29:AB:75:AF:9B:5F:2F:CD:35:33:B9:5C:7B:79:93:B6:A4:C2:4E:41:58:C0:0C:AB:67:81
SHA1
07:22:C2:43:EC:CF:0A:D1:34:37:0E:CC:D4:19:E1:C6:41:7B:3A:85
X509v3 extensions
subjectKeyIdentifier
  • 6B:14:FF:F6:60:66:04:D4:D3:F2:D3:53:D5:66:AD:A1:AE:9D:DF:6F
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Apr 10 09:29:50.287 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:26:03:CB:33:4F:D3:4E:DC:D8:CA:4E:14:
  • F3:00:42:4C:68:19:49:BA:A7:DD:D3:39:ED:99:85:8E:
  • 1E:24:2F:D7:02:21:00:E3:71:02:66:BF:BA:0E:78:59:
  • 82:54:A9:DE:94:72:F8:6F:45:70:1E:03:A1:E7:C2:9D:
  • 83:13:7C:70:F2:98:64
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 10 09:29:50.305 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:55:9C:83:48:55:48:64:16:82:83:7E:F8:
  • A9:DC:81:9D:71:16:C5:15:7E:A0:6E:74:DF:1E:63:97:
  • F0:00:BB:76:02:21:00:B4:0F:C0:48:76:83:DB:81:E0:
  • B1:31:43:54:EE:61:8B:6E:EA:FD:57:29:1E:CA:36:68:
  • 12:0F:FA:41:72:9B:02