SSL-Tools

SSL check results of migrate00.raketaro.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for migrate00.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:57:03 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

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

Certificates

First seen at:

CN=raketaro.de

Certificate chain
  • raketaro.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • raketaro.de
Alternative Names
  • migrate00.raketaro.de
  • raketaro.de
  • www.raketaro.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-11-05
Not valid after
2025-02-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DF:F2:DA:D2:D8:47:82:63:B6:57:27:65:8E:00:DD:44:EB:10:92:50:AA:2D:AC:77:08:4D:C2:D8:4F:9C:02:B8
SHA1
69:60:A0:DF:2F:F9:BC:18:EE:25:F5:CB:28:82:4A:CF:87:B8:A0:85
X509v3 extensions
subjectKeyIdentifier
  • 75:D5:F4:6D:EE:8E:F5:43:BE:6D:28:C3:01:3E:2A:A8:E8:27:D3:A0
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.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 : Nov 5 05:16:10.601 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:60:9F:A3:75:8A:E0:C3:C5:4A:CE:0D:15:
  • 99:33:F1:B2:3D:46:E6:EC:06:D7:80:CD:13:5B:F4:AC:
  • 11:8C:BE:43:02:20:37:04:12:41:52:1B:73:CE:3F:14:
  • 8D:9E:6A:43:FF:37:84:A2:CD:3F:B9:DF:0E:9E:D4:93:
  • E0:1D:06:8A:57:78
  • 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 : Nov 5 05:16:10.728 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:86:09:A3:5B:80:55:74:58:27:06:D8:
  • 63:58:C8:FD:2D:65:B7:F0:78:0D:52:28:B5:DB:D8:ED:
  • AE:D7:43:88:F1:02:21:00:E4:B6:9A:15:4D:64:7F:1A:
  • B3:68:CC:5A:E8:34:09:1E:30:80:87:4C:BA:7B:04:9F:
  • F3:25:0B:75:DB:A4:9D:60

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