SSL-Tools

SSL check results of ptmail.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for ptmail.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 Tue, 24 Sep 2024 12:06:53 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.ptmail.de
2a03:4000:2a:60a::2
 10
supported
mx.ptmail.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mx.ptmail.de
193.30.123.83
 10
supported
mx.ptmail.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 received emails from these servers with @ptmail.de sender addresses. Test mail delivery

Host TLS Version & Cipher
mx.ptmail.de (193.30.123.83)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mx.ptmail.de

Certificate chain
  • mx.ptmail.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)
  • mx.ptmail.de
Alternative Names
  • mx.ptmail.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-22
Not valid after
2024-12-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
46:43:6C:ED:91:A5:01:46:40:82:FC:46:60:32:81:8B:27:A3:CF:D4:53:B8:D3:61:6F:AE:75:E0:18:85:25:E1
SHA1
85:91:28:0D:6F:26:BA:14:A8:FF:E6:18:91:F4:7D:72:5E:FE:4E:5C
X509v3 extensions
subjectKeyIdentifier
  • 6B:6F:A9:30:5A:A3:78:1D:39:44:AA:98:FF:E3:A4:5E:67:55:D9:97
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 22 03:47:13.528 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:75:86:D5:A2:EF:FE:47:E9:DE:DB:5E:93:
  • A5:11:C1:00:D8:8F:5F:E6:B7:0B:68:76:03:E1:32:E1:
  • DC:D6:ED:0A:02:21:00:80:34:7B:34:73:6A:2C:82:4B:
  • 27:61:35:7D:68:31:EC:14:99:E4:CF:5B:B7:3F:0A:8A:
  • E3:32:B3:3A:D3:CB:ED
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Sep 22 03:47:13.757 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E6:5D:89:DB:19:54:4D:B7:F7:2B:88:
  • 7C:28:C3:1D:1A:9F:64:2C:D4:AD:5A:02:49:FF:FE:09:
  • 11:80:0D:26:BC:02:20:0F:3A:89:FA:63:96:1B:A3:1C:
  • CB:BC:F2:3F:56:4F:96:42:E2:3F:CA:23:55:9E:81:8F:
  • C3:CB:F2:F0:39:BD:DE