SSL-Tools

SSL check results of archify.fr

NEW You can also bulk check multiple servers.

Discover if the mail servers for archify.fr 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, 10 Jun 2025 15:55:21 +0000

The mailservers of archify.fr can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @archify.fr addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.alwaysdata.com
2a00:b6e0:1:42:1::1
 10
supported
*.alwaysdata.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mx1.alwaysdata.com
185.31.40.80
 10
supported
*.alwaysdata.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mx2.alwaysdata.com
2a00:b6e0:2:42:1::1
 20
supported
*.alwaysdata.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mx2.alwaysdata.com
78.142.219.80
 20
supported
*.alwaysdata.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.alwaysdata.com

Certificate chain
  • *.alwaysdata.com
    • 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)
  • *.alwaysdata.com
Alternative Names
  • *.alwaysdata.com
  • alwaysdata.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-05-20
Not valid after
2025-08-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
16:3C:74:4A:F5:55:A8:4D:C6:8D:CF:64:94:3B:51:2E:6F:E9:29:4D:65:42:0C:A0:50:4C:94:2C:41:3C:8B:51
SHA1
39:E3:C7:63:F7:70:D6:73:2A:01:0C:E1:9D:7D:B6:BF:D0:E6:A2:47
X509v3 extensions
subjectKeyIdentifier
  • DE:13:B6:52:16:98:69:3A:57:36:BD:31:8D:DA:86:D8:C2:30:A3:93
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e5.c.lencr.org/113.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : May 20 06:21:26.875 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:90:DF:90:DE:49:36:58:F5:EF:18:CA:
  • B4:AD:EC:0A:C6:21:32:E5:48:93:7B:F9:09:33:7A:00:
  • EB:3F:3A:3B:9F:02:21:00:A9:3D:26:62:90:5D:99:94:
  • 86:9A:DE:60:77:DB:79:F8:FD:0A:BD:08:B6:F7:4E:59:
  • 74:49:48:70:97:30:07:22
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : May 20 06:21:28.891 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DB:01:FC:57:C2:7A:95:B5:76:88:97:
  • D6:C7:31:83:F8:C1:CF:3A:7F:4B:28:AF:D3:AE:3D:0C:
  • 31:38:19:20:1D:02:20:5E:D9:34:5F:8F:DB:57:E9:D2:
  • 11:7E:59:DB:E7:E6:B4:A6:8C:32:88:DB:1C:69:B0:9F:
  • 4D:26:4A:81:65:32:F9