SSL-Tools

SSL check results of mail.viaraetia.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.viaraetia.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 Thu, 13 Mar 2025 17:16:54 +0000

The mailservers of mail.viaraetia.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.viaraetia.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.viaraetia.org
172.232.211.39
 -
supported
viaraetia.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.viaraetia.org
2600:3c0b::f03c:95ff:fe7a:ac4a
 -
supported
viaraetia.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=viaraetia.org

Certificate chain
  • viaraetia.org
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • viaraetia.org
Alternative Names
  • *.viaraetia.org
  • viaraetia.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-01-26
Not valid after
2025-04-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
63:36:DE:CD:42:16:A3:3A:E6:CA:7B:9E:F7:75:F2:39:76:87:B0:37:13:18:36:67:86:A5:AB:10:71:97:93:88
SHA1
FC:11:FE:A3:23:B9:62:72:FB:F1:13:7A:A4:CF:F4:09:75:DE:22:22
X509v3 extensions
subjectKeyIdentifier
  • 8C:F5:11:DB:16:78:05:41:61:FF:6C:D9:60:80:56:13:D8:61:D7:E7
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Jan 26 12:39:05.688 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E8:E8:E9:9C:0B:CC:DF:D7:E1:40:DA:
  • 8A:F4:98:EC:A3:F6:FF:24:FF:95:2F:6B:8B:A0:32:F0:
  • BC:39:24:75:E6:02:21:00:91:D9:58:75:8A:47:D2:DB:
  • ED:E0:1E:48:D7:05:01:27:28:46:04:4F:91:98:12:FB:
  • E6:E1:80:21:1B:4C:D8:12
  • 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 26 12:39:05.690 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EC:04:AC:0C:5B:22:02:ED:61:0D:00:
  • 2A:9C:DC:11:C2:3C:6E:32:75:A5:E5:36:F9:2D:C2:59:
  • 80:BA:AD:47:8F:02:21:00:C1:BA:79:2C:03:00:C8:E5:
  • A6:83:F9:07:47:5F:1D:52:D5:8C:57:CC:11:BF:7A:09:
  • 06:5C:3F:7E:6F:D7:BA:8A