SSL-Tools

SSL check results of enviatel-business.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for enviatel-business.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 Mon, 27 Jan 2025 01:30:30 +0000

The mailservers of enviatel-business.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @enviatel-business.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.postale.io
3.139.204.210
 0
supported
mail.postale.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
27 s
mail.postale.io
3.136.239.197
 0
supported
mail.postale.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
26 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.postale.io

Certificate chain
  • mail.postale.io
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.postale.io
Alternative Names
  • autoconfig.postale.io
  • autodiscover.postale.io
  • imap.postale.io
  • mail.postale.io
  • pop.postale.io
  • postale.io
  • smtp.postale.io
  • status.postale.io
  • webmail.postale.io
  • www.postale.io
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-01-20
Not valid after
2025-04-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
00:B4:B1:E7:05:0E:8A:A5:F7:63:1E:59:20:54:29:C3:E1:48:03:36:E9:75:68:FC:CF:C2:84:E3:0A:52:F2:86
SHA1
5D:B6:E8:F9:C5:32:8B:B2:0E:89:CB:41:69:C4:38:50:74:42:3B:B4
X509v3 extensions
subjectKeyIdentifier
  • 21:B0:6F:AC:81:BF:08:C7:54:6A:21:48:96:45:4B:08:77:B2:3A:6F
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.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 : Jan 20 06:25:19.186 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:87:49:EB:94:05:35:AA:11:08:67:68:
  • 01:EE:99:51:11:42:EE:6B:6D:4B:EF:47:CB:E3:6C:96:
  • CF:D3:EE:02:14:02:21:00:C8:80:D8:AE:4D:7A:B3:EA:
  • 40:5A:3D:FE:70:90:0A:C5:FE:5F:DC:FC:5B:C3:ED:41:
  • A0:CA:E9:CE:CF:B4:B8:E5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Jan 20 06:25:19.277 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9D:12:D1:41:17:9E:88:21:17:49:A5:
  • 1C:CB:43:50:E4:FE:00:EC:3A:9C:CF:26:6F:E9:FB:F9:
  • 05:00:43:B8:2E:02:21:00:FC:BD:BE:54:77:82:C5:7A:
  • 4A:1B:D4:DB:44:50:26:A8:32:BF:5D:2D:ED:98:8B:EA:
  • 36:FA:CA:49:D6:FC:0C:41