SSL-Tools

SSL check results of futurement.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for futurement.net 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 Fri, 29 Aug 2025 19:00:38 +0000

The mailservers of futurement.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @futurement.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
rmf02.raebbit.com
2a01:4f8:c012:c274::1
 10
supported
rmf02.raebbit.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
rmf02.raebbit.com
49.13.58.26
 10
supported
rmf02.raebbit.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
rmf01.raebbit.com
2a01:4f8:1c1b:a25b::1
 20
supported
rmf01.raebbit.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
rmf01.raebbit.com
78.47.62.240
 20
supported
rmf01.raebbit.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=rmf01.raebbit.com

Certificate chain
Subject
Common Name (CN)
  • rmf01.raebbit.com
Alternative Names
  • rmf01.raebbit.com
Issuer
Country (C)
  • AT
Organization (O)
  • ZeroSSL
Common Name (CN)
  • ZeroSSL ECC Domain Secure Site CA
validity period
Not valid before
2025-08-12
Not valid after
2025-11-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DE:72:3B:E5:5F:48:55:73:A6:7B:64:77:3C:ED:E4:E5:91:60:A2:13:98:4A:64:3C:06:E1:04:98:44:67:5C:2A
SHA1
23:71:70:BC:80:72:64:6D:4B:B3:1C:CB:B4:59:CF:87:EC:DC:CB:86
X509v3 extensions
authorityKeyIdentifier
  • keyid:0F:6B:E6:4B:CE:39:47:AE:F6:7E:90:1E:79:F0:30:91:92:C8:5F:A3
subjectKeyIdentifier
  • CB:DA:74:2E:59:CF:7D:12:FC:14:FE:EB:F3:DA:BA:1B:95:FD:B9:09
certificatePolicies
  • Policy: 1.3.6.1.4.1.6449.1.2.2.78
  • CPS: https://sectigo.com/CPS
  • Policy: 2.23.140.1.2.1
authorityInfoAccess
  • CA Issuers - URI:http://zerossl.crt.sectigo.com/ZeroSSLECCDomainSecureSiteCA.crt
  • OCSP - URI:http://zerossl.ocsp.sectigo.com
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Aug 12 22:58:55.148 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:31:51:9C:3A:8E:17:16:6A:7B:47:60:FC:
  • 78:EB:6C:9D:EF:9F:1E:93:CA:89:C5:D3:58:37:21:4D:
  • 4C:A0:05:2F:02:21:00:CB:CC:10:19:7E:C2:83:4D:36:
  • 08:AA:9B:DC:D4:E2:26:71:69:A8:A0:ED:A9:34:70:D9:
  • FB:F7:BA:C8:72:FC:B5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Aug 12 22:58:55.145 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:70:67:22:95:10:03:D0:95:74:94:8C:1D:
  • 1C:85:41:0A:04:77:B0:2D:5B:FF:E5:11:03:D6:C4:8C:
  • F0:4B:76:7E:02:20:32:02:B0:C2:07:DD:0F:6E:E9:C2:
  • F0:63:85:D1:E9:BA:FB:41:E1:AE:7A:26:58:BD:03:00:
  • 97:DB:18:C6:1B:F7
First seen at:

CN=rmf02.raebbit.com

Certificate chain
Subject
Common Name (CN)
  • rmf02.raebbit.com
Alternative Names
  • rmf02.raebbit.com
Issuer
Country (C)
  • AT
Organization (O)
  • ZeroSSL
Common Name (CN)
  • ZeroSSL ECC Domain Secure Site CA
validity period
Not valid before
2025-08-12
Not valid after
2025-11-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
03:D8:A1:B1:FE:DD:C0:0F:50:13:82:D4:0E:A3:8F:B6:27:2E:1C:D1:0F:CC:38:80:4C:FB:52:79:8A:A2:5E:63
SHA1
AA:D8:32:8D:03:15:02:7B:B5:42:B9:43:C6:08:BF:4E:17:D4:2E:30
X509v3 extensions
authorityKeyIdentifier
  • keyid:0F:6B:E6:4B:CE:39:47:AE:F6:7E:90:1E:79:F0:30:91:92:C8:5F:A3
subjectKeyIdentifier
  • 01:B6:09:47:06:8D:32:B0:71:54:45:FE:E5:78:0D:A9:27:52:76:16
certificatePolicies
  • Policy: 1.3.6.1.4.1.6449.1.2.2.78
  • CPS: https://sectigo.com/CPS
  • Policy: 2.23.140.1.2.1
authorityInfoAccess
  • CA Issuers - URI:http://zerossl.crt.sectigo.com/ZeroSSLECCDomainSecureSiteCA.crt
  • OCSP - URI:http://zerossl.ocsp.sectigo.com
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Aug 12 22:59:55.779 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:93:01:DD:24:58:25:78:2A:56:43:63:
  • A8:9A:98:F2:51:47:F7:FF:2D:CD:C8:9D:F9:F3:79:19:
  • 55:9F:A6:AC:F7:02:20:13:93:FC:BC:0D:81:08:02:ED:
  • 17:E3:FE:06:7B:6C:50:A8:2D:B4:BE:C5:57:AC:61:25:
  • A9:A1:53:DB:91:FA:C1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Aug 12 22:59:55.810 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A8:3F:7E:83:58:8A:5C:34:FC:2F:96:
  • 0D:55:10:90:95:6E:7E:D9:6D:81:9F:BB:26:76:C5:F9:
  • F9:4A:9B:F7:54:02:20:4D:B4:DC:6B:C9:04:CB:4F:FE:
  • 5D:3B:AB:04:D7:28:5A:38:4E:17:E5:65:68:52:74:34:
  • D2:61:AF:C5:48:06:B1