SSL-Tools

SSL check results of criptomaniacos.email

NEW You can also bulk check multiple servers.

Discover if the mail servers for criptomaniacos.email 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 Wed, 27 Mar 2024 23:52:54 +0000

The mailservers of criptomaniacos.email can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @criptomaniacos.email addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
alt2.aspmx.l.google.com
2a00:1450:4025:c03::1a
Results incomplete
5
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
alt2.aspmx.l.google.com
142.251.9.26
Results incomplete
5
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
my.cmania.co
89.116.73.231
 10
supported
my.cmania.co
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=my.cmania.co

Certificate chain
  • my.cmania.co
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • my.cmania.co
Alternative Names
  • my.cmania.co
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-27
Not valid after
2024-06-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8B:C0:D2:EB:64:A2:3D:43:63:20:A3:45:B9:9A:54:1E:9F:F4:54:C3:14:9C:15:FC:D9:5F:DF:1C:C9:44:A3:27
SHA1
72:56:72:9B:34:25:60:39:F8:DA:D2:30:DC:F6:2B:AC:37:11:E1:37
X509v3 extensions
subjectKeyIdentifier
  • 62:46:41:7F:62:58:AE:35:4C:9C:88:52:AF:4C:8C:E8:83:9E:C0:95
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 27 14:07:40.946 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AB:BE:02:00:DD:7B:50:81:4D:4A:30:
  • E7:C1:2C:E4:40:3E:24:6C:14:05:6D:20:A7:07:9E:71:
  • D2:B7:61:DB:30:02:21:00:D7:4A:20:CA:6B:8D:EE:F9:
  • FD:F0:3A:6A:7F:54:E2:8B:59:0F:2C:43:06:D5:3B:62:
  • E7:39:D2:AA:0B:39:69:E2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Mar 27 14:07:42.946 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:85:4E:93:5D:0D:8F:85:B3:E6:F8:4A:
  • 05:82:DC:19:3C:1F:11:58:22:F6:E3:39:BF:4A:00:7C:
  • D0:4D:03:0A:B6:02:20:75:6D:A2:B7:3A:0E:A9:80:5A:
  • D9:CB:8B:0F:7D:C4:C6:35:74:EB:1D:0E:22:EA:F8:9D:
  • 09:FA:DD:BE:C8:ED:B3