SSL-Tools

SSL check results of mx.jaltadaheerd.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for mx.jaltadaheerd.nl 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 Wed, 17 Apr 2024 15:24:40 +0000

The mailservers of mx.jaltadaheerd.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mx.jaltadaheerd.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.jaltadaheerd.nl
147.78.236.183
 -
supported
jaltadaheerd.nl
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mx.jaltadaheerd.nl
2a0f:2980:100:1201:211:32ff:feb4:3521
 -
supported
jaltadaheerd.nl
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s

Outgoing Mails

We have not received any emails from a @mx.jaltadaheerd.nl address so far. Test mail delivery

Certificates

First seen at:

CN=jaltadaheerd.nl

Certificate chain
  • jaltadaheerd.nl
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • jaltadaheerd.nl
Alternative Names
  • *.jaltadaheerd.nl
  • jaltadaheerd.nl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-25
Not valid after
2024-05-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
72:3B:2B:F0:20:0B:FA:93:E3:CC:38:90:3F:6E:AB:ED:CC:3C:8A:B2:83:C0:83:E4:F7:08:8B:2E:31:AC:7F:54
SHA1
B6:B4:3F:09:62:3B:D2:2D:36:E0:A3:AC:F1:00:CC:2D:E8:F1:B3:21
X509v3 extensions
subjectKeyIdentifier
  • 5C:B2:85:CB:74:C1:F9:39:37:33:5B:18:12:1C:EA:77:18:CE:22:A3
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 : Feb 25 05:26:30.958 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:01:6C:E2:8E:C9:53:3A:2B:3D:2D:6F:97:
  • 0E:99:05:3C:B9:81:10:2E:3D:13:AE:40:36:8D:9F:3E:
  • 1A:D0:BC:28:02:21:00:D2:DC:50:06:57:E8:4F:89:9E:
  • 4B:6F:A8:5F:BA:7F:36:1F:30:77:8A:6E:FD:01:4C:85:
  • 5F:90:EA:21:02:AB:15
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Feb 25 05:26:30.966 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AE:59:C3:CD:49:B3:B8:FB:53:E3:B8:
  • B0:27:87:15:38:81:D6:72:B6:FC:F8:9A:54:50:D5:2C:
  • 2A:15:AE:76:F9:02:20:13:BF:0E:37:B9:8A:40:64:7D:
  • 83:EB:20:D2:F6:6F:C7:9E:BE:15:26:2B:A7:1D:9D:00:
  • 03:10:3F:5A:48:BA:A0

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mx.jaltadaheerd.nl
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid