SSL-Tools

SSL check results of migrate02.raketaro.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for migrate02.raketaro.de 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, 05 Nov 2024 06:56:10 +0000

The mailservers of migrate02.raketaro.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @migrate02.raketaro.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
migrate02.raketaro.de
167.235.201.7
 -
supported
migrate02.raketaro.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
migrate02.raketaro.de
2a01:4f8:c012:5c92::1
 -
supported
migrate02.raketaro.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

We have not received any emails from a @migrate02.raketaro.de address so far. Test mail delivery

Certificates

First seen at:

CN=migrate02.raketaro.de

Certificate chain
  • migrate02.raketaro.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • migrate02.raketaro.de
Alternative Names
  • migrate02.raketaro.de
  • mta-sts.raketaro.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-10-27
Not valid after
2025-01-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B7:C5:16:43:64:E4:16:D0:47:11:59:94:E3:6A:23:F0:3A:36:2F:AC:71:8B:4B:80:47:47:7C:81:FF:7F:40:64
SHA1
B4:EF:47:72:6A:A1:52:D4:DB:33:E5:87:E5:5B:9A:99:A0:D2:5D:D1
X509v3 extensions
subjectKeyIdentifier
  • 63:C6:98:DC:65:61:0E:0B:6A:83:25:11:7D:37:DF:FA:E2:C1:FC:FD
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Oct 27 12:22:26.000 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:70:F4:F3:A2:D8:37:6A:F0:AD:6F:21:C6:
  • 03:C7:0B:D3:E5:A4:55:66:9D:C9:76:71:8B:88:5C:FB:
  • 6F:68:0D:42:02:20:08:70:8D:6B:28:49:4D:4F:81:78:
  • 56:72:10:85:2E:30:DB:CE:0F:D9:60:B4:AE:59:2F:43:
  • 8B:05:DC:21:5D:5F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Oct 27 12:22:26.025 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F4:E8:F3:11:F0:40:6E:08:60:3C:CC:
  • 0C:A6:D1:AF:1A:94:95:81:15:14:0C:13:8B:12:A6:BE:
  • BE:7B:9B:93:02:02:21:00:CB:7B:25:23:DC:74:85:4F:
  • 06:6B:FD:6D:93:92:B1:FA:98:9F:E7:A7:F6:95:A9:A0:
  • EF:BC:7F:7E:26:88:04:88

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.migrate02.raketaro.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid