SSL check results of t9p.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for t9p.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, 15 Feb 2025 18:19:21 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.t9p.de
2a03:4000:4b:71::1
10
supported
mail.t9p.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.t9p.de
45.157.178.67
10
supported
mail.t9p.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.t9p.de

Certificate chain
  • mail.t9p.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.t9p.de
Alternative Names
  • mail.t9p.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-12-06
Not valid after
2025-03-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FF:5D:28:E3:70:0D:FC:9A:86:74:24:72:D5:55:7B:70:7B:93:7E:BD:7E:93:2D:38:A1:EB:FF:0E:79:EF:00:AE
SHA1
46:63:5D:F1:44:33:07:5A:B9:9E:D6:B3:FD:12:CF:8C:9A:92:EA:6D
X509v3 extensions
subjectKeyIdentifier
  • B3:4D:FB:C6:89:DB:D7:3C:01:29:B9:47:9B:42:41:F8:FD:44:B4:EE
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Dec 6 16:18:18.902 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7C:59:33:2A:0D:D0:74:D5:CA:DC:F3:AD:
  • 2F:3C:A1:2C:F4:86:04:98:D7:59:5E:06:64:31:44:87:
  • 90:9D:AC:1B:02:20:2A:EB:CA:8B:88:0D:25:A1:64:86:
  • 06:6A:E9:07:4A:54:3D:0F:82:70:69:52:FE:68:E6:16:
  • 67:08:8B:9B:64:CF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Dec 6 16:18:19.187 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BA:2F:91:A4:DD:65:F6:3E:B3:12:AB:
  • 67:C7:48:E8:1A:8D:C6:44:B9:0D:6D:CB:AF:C2:F8:A5:
  • 9A:EA:D2:10:66:02:20:5E:2F:9E:4D:6A:E4:A3:68:0B:
  • 23:59:F3:E7:91:52:A7:48:9C:F1:B8:3A:83:43:5F:E7:
  • 9A:AD:72:97:28:DF:BD