SSL check results of mojo.cc

NEW You can also bulk check multiple servers.

Discover if the mail servers for mojo.cc 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

Report created Tue, 23 Feb 2021 12:14:30 +0000

The mailservers of mojo.cc can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mojo.cc addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mojo.cc
2a01:4f8:160:5095::72
10
supported
mojo.cc
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.mojo.cc
148.251.207.72
10
supported
mojo.cc
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @mojo.cc sender addresses. Test mail delivery

Host TLS Version & Cipher
unknown (IPv6:2a01:4f8:160:5095::2)
TLSv1.3 TLS_AES_256_GCM_SHA384
mx.mojo.cc (88.198.84.0)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mojo.cc

Certificate chain
  • mojo.cc
    • remaining
    • 384 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • mojo.cc
Alternative Names
  • *.mojo.cc
  • mojo.cc
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-16
Not valid after
2021-05-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3A:39:CE:26:C2:A9:AD:77:2D:66:04:7B:A5:13:F0:8E:3C:36:5F:28:E6:7D:DD:35:96:19:04:46:B3:A1:3F:13
SHA1
AD:A0:D7:F2:B8:4C:64:FA:A8:4C:10:74:2D:E5:5B:83:DE:D7:D0:FB
X509v3 extensions
subjectKeyIdentifier
  • E1:83:34:C5:54:02:F9:5B:E7:F0:08:53:B4:04:04:8F:E5:78:A4:6B
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Feb 16 21:51:25.007 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5B:62:FD:2A:0C:E4:04:52:B1:3A:6B:AF:
  • FB:BE:3B:AF:5C:9A:91:56:A4:EB:F9:FC:64:25:C5:70:
  • B2:AF:89:1A:02:21:00:F3:1F:E4:B2:A3:36:A7:94:9B:
  • 47:AA:8F:8B:86:F4:60:5A:4E:A8:37:54:E2:F3:AC:7C:
  • 48:E3:CC:E5:6E:0C:E1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Feb 16 21:51:25.019 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AA:1E:6F:9C:07:D5:79:77:3E:7B:36:
  • B2:56:E3:2A:CB:3F:D5:52:43:51:E3:C3:1B:E3:D3:98:
  • 2B:6F:50:78:AB:02:21:00:FD:F9:55:02:88:98:0F:08:
  • 65:CB:E1:4D:66:F5:3F:A5:28:59:55:A7:23:38:A9:16:
  • C2:9B:26:C2:D1:27:8F:94

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.mail.mojo.cc
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
error
Debug
valid