SSL-Tools

SSL check results of pvtm.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for pvtm.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 Thu, 25 Apr 2024 19:29:54 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.pvtm.de
2a01:4f8:1c0c:4227::1
 10
supported
mail.pvtm.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s
mail.pvtm.de
5.75.189.214
 10
supported
mail.pvtm.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.pvtm.de

Certificate chain
  • mail.pvtm.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.pvtm.de
Alternative Names
  • mail.pvtm.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-25
Not valid after
2024-07-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
39:E2:27:33:55:D5:BD:17:C5:D8:F0:95:45:A2:DB:DE:5B:DF:12:E2:BD:FE:AE:FC:51:6D:A2:7B:F3:8A:9E:F8
SHA1
55:4C:1B:BE:7A:A9:E7:AE:98:45:9C:22:F8:6F:A6:9E:D5:2B:6C:4B
X509v3 extensions
subjectKeyIdentifier
  • 02:B6:10:03:21:BC:58:63:9A:66:8D:41:E1:A6:EF:91:2E:AD:7B:54
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 : 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 : Apr 25 16:55:52.262 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5A:90:F1:AB:EC:F6:7F:C0:6F:3E:F1:78:
  • FC:66:F4:F3:2B:56:18:15:2A:F7:56:20:15:AC:E7:1F:
  • B4:A7:C8:55:02:20:0E:C8:7E:25:4A:29:D3:50:BC:C5:
  • FF:80:AD:CB:38:2B:BD:F4:8B:28:E5:AC:54:BE:46:E9:
  • 6A:18:62:48:A4:78
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 25 16:55:52.336 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:04:24:E0:39:29:2A:09:D9:C1:46:07:B0:
  • E9:F5:21:A3:5F:23:11:7E:24:DB:2E:FE:CB:A1:27:EA:
  • D7:51:41:25:02:20:7B:4A:56:A1:C8:60:B3:5B:9A:9F:
  • F3:4E:4E:D2:B9:F0:54:33:90:55:75:03:E3:DA:65:70:
  • 58:D0:75:AB:97:73