SSL-Tools

SSL check results of rojoma.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for rojoma.com 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, 16 Apr 2024 16:29:31 +0000

The mailservers of rojoma.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rojoma.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rojoma.com
2a01:7e00::f03c:92ff:febb:196f
 10
supported
rojoma.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.rojoma.com
212.71.244.243
 10
supported
rojoma.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=rojoma.com

Certificate chain
  • rojoma.com
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • rojoma.com
Alternative Names
  • dev.eternal-flame.org
  • eternal-flame.org
  • git.rojoma.com
  • irc.eternal-flame.org
  • irc.rojoma.com
  • lattice.rojoma.com
  • mail.rojoma.com
  • rojoma.com
  • v4.eternal-flame.org
  • v4.rojoma.com
  • v6.eternal-flame.org
  • v6.rojoma.com
  • www.eternal-flame.org
  • www.rojoma.com
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
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
85:73:86:29:06:5B:4D:26:0E:18:B4:52:09:E3:16:12:4A:33:EC:8B:26:35:14:85:B2:1E:0F:53:06:50:13:A0
SHA1
DE:96:11:19:D1:EF:D1:83:0D:01:61:66:2C:57:94:0E:DF:0A:B6:F8
X509v3 extensions
subjectKeyIdentifier
  • 54:42:21:03:0B:FF:7E:89:16:52:75:B7:1A:3A:7B:72:1E:CC:01:8B
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 : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 16 16:24:58.308 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:55:1E:65:EA:8E:64:8C:5B:E9:2E:B8:40:
  • D3:33:8B:78:52:F7:88:71:42:77:4D:CD:48:A2:51:46:
  • 50:76:5E:E5:02:20:54:26:D0:59:A1:41:92:58:C2:6B:
  • 46:E0:65:E6:43:F7:DB:3D:71:D4:31:A6:B0:E7:C2:13:
  • 3D:AA:0B:6C:90:9E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 16 16:24:58.500 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DB:C9:DE:27:0A:C2:80:BC:F6:B3:63:
  • D0:1D:2C:1F:22:7A:FA:21:98:66:53:4C:1C:1B:1E:49:
  • CC:DE:65:84:DA:02:20:51:EB:D0:72:3B:88:E0:62:F7:
  • FB:7D:1A:62:18:BE:B7:6E:6B:8B:55:CC:E4:17:7D:5D:
  • 19:17:67:E8:AB:A1:F6