SSL check results of alldis.tech

NEW You can also bulk check multiple servers.

Discover if the mail servers for alldis.tech 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

Report created Tue, 16 Apr 2024 19:45:10 +0000

The mailservers of alldis.tech can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @alldis.tech addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
alldis.tech
91.236.197.246
-
supported
alldis.tech
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
alldis.tech
91.105.196.168
-
supported
alldis.tech
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=alldis.tech

Certificate chain
  • alldis.tech
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • alldis.tech
Alternative Names
  • *.alldis.tech
  • alldis.tech
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-16
Not valid after
2024-07-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A5:98:8D:45:98:15:0F:10:A2:45:67:D5:BE:26:52:5D:04:04:8B:C7:AA:2A:8A:80:4B:FE:2A:E3:84:2E:C5:18
SHA1
25:41:E2:2A:49:3B:DC:E7:4C:5D:28:CF:44:F7:84:02:A7:FB:65:38
X509v3 extensions
subjectKeyIdentifier
  • 4D:49:16:CE:A2:18:28:FF:41:38:F8:2F:5E:4E:D3:1C:8F:70:EC:CF
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 16 19:38:07.455 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0E:68:40:A7:7F:FB:F6:77:C2:53:AC:65:
  • A2:B8:7B:B8:ED:37:17:C6:57:DB:89:2A:80:4C:A7:BC:
  • 22:0E:89:50:02:21:00:FA:28:EA:12:E9:67:60:E5:21:
  • 20:F6:D8:CA:25:EA:80:F8:5E:19:73:4E:90:CD:18:19:
  • 6A:5D:E9:D3:54:A7:06
  • 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 16 19:38:07.526 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C4:FC:27:03:05:DF:75:4B:08:ED:48:
  • 36:FA:F6:44:63:2A:6B:AB:06:52:05:D0:CA:13:CE:F2:
  • 5C:B2:7C:66:42:02:21:00:93:C9:86:66:F3:FF:5C:37:
  • DC:A7:88:C2:F4:58:E4:33:90:98:EC:BA:D3:9D:92:4A:
  • 0A:88:85:36:2F:30:87:8B