SSL-Tools

SSL check results of 4netmail.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for 4netmail.org 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, 17 Mar 2025 14:04:12 +0000

The mailservers of 4netmail.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @4netmail.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.4netmail.org
2a03:4000:29:5aa::b182:4444
 10
supported
mail.4netmail.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.4netmail.org
94.16.117.107
 10
supported
mail.4netmail.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

We have received emails from these servers with @4netmail.org sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.4netmail.org (IPv6:2a03:4000:29:5aa::b182:4444)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.4netmail.org

Certificate chain
  • mail.4netmail.org
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.4netmail.org
Alternative Names
  • autoconfig.4netmail.org
  • autodiscover.4netmail.org
  • mail.4netmail.org
  • mta-sts.4netguides.org
  • mta-sts.4netmail.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-02-04
Not valid after
2025-05-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
85:69:6F:D5:67:8E:D3:82:8E:84:84:AD:A4:26:87:3A:40:E8:47:97:C5:6D:7C:A3:D7:D3:3F:70:1D:6E:A9:D4
SHA1
85:48:0C:AE:84:37:69:D4:D5:D6:FD:38:CE:8E:2F:3B:63:4A:03:FF
X509v3 extensions
subjectKeyIdentifier
  • 23:8C:71:DF:E7:52:18:3D:A3:3D:D1:EB:52:98:40:F6:C8:6E:1F:2B
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 : Feb 4 18:44:51.206 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AD:F6:11:57:46:80:5A:2C:78:67:CE:
  • 27:F2:66:23:F8:14:EC:23:46:68:96:4B:35:94:4F:2B:
  • BA:B0:34:2B:4E:02:20:61:CD:F3:29:7E:03:EB:23:DC:
  • 2D:EF:A6:A9:17:61:28:91:A7:48:9D:DA:6E:CF:AE:6A:
  • C1:85:4B:F7:47:4E:D5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Feb 4 18:44:51.269 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5A:26:F6:0A:33:86:07:CB:3F:52:81:6B:
  • 80:B9:93:F5:2F:A3:F9:DC:DC:EA:6C:CA:36:01:49:76:
  • E6:61:FE:03:02:20:65:35:B2:FE:A6:E2:51:C5:D1:2B:
  • FB:2E:08:0F:21:21:43:13:3D:F2:6B:0C:FD:9C:39:24:
  • 0E:5C:A3:06:22:C5