SSL-Tools

SSL check results of smtp.gentlent.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for smtp.gentlent.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 Thu, 25 Nov 2021 17:18:20 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.gentlent.net
94.130.130.53
 -
supported
*.gentlent.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s
smtp.gentlent.net
2a01:4f8:13b:39ca::2
 -
supported
*.gentlent.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.gentlent.com

Certificate chain
  • *.gentlent.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • ISRG Root X2
            • remaining
            • 384 bit
            • sha256WithRSAEncryption
              • ISRG Root X1 (Certificate is self-signed.)
                • remaining
                • 4096 bit
                • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.gentlent.com
Alternative Names
  • *.gentlent.com
  • *.gentlent.net
  • *.staging.gentlent.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E1
validity period
Not valid before
2021-11-13
Not valid after
2022-02-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
ED:2C:CF:35:67:30:EA:D2:2D:74:70:AD:FE:1F:81:04:B5:E1:32:3F:E6:EA:BA:3B:AE:39:F6:6E:4A:C3:DB:EB
SHA1
D0:71:55:BE:DF:CE:F3:C6:7D:37:2F:0A:95:64:C9:07:CB:7A:CE:CB
X509v3 extensions
subjectKeyIdentifier
  • A0:F5:6B:1C:E5:07:A9:1B:49:C9:F3:34:3F:4A:11:C9:81:3F:0A:D5
authorityKeyIdentifier
  • keyid:5A:F3:ED:2B:FC:36:C2:37:79:B9:52:30:EA:54:6F:CF:55:CB:2E:AC
authorityInfoAccess
  • OCSP - URI:http://e1.o.lencr.org
  • CA Issuers - URI:http://e1.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 : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Nov 13 18:44:03.847 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E8:DA:5F:0B:66:97:38:3F:AF:92:DE:
  • A3:3B:67:1C:69:DA:A5:49:88:0E:05:C0:76:F4:A8:C8:
  • 63:25:0E:12:13:02:21:00:DE:48:9E:08:7E:34:39:84:
  • 89:86:32:08:4E:2D:C7:D4:6F:AD:EE:32:1B:DE:81:A6:
  • AC:0E:81:78:99:30:3E:7E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : Nov 13 18:44:04.372 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A2:C5:F6:69:8D:4B:71:CF:6D:CB:63:
  • 1C:91:D8:02:62:DB:36:AE:5D:EC:BE:47:F3:07:EE:68:
  • 46:DB:E6:43:D6:02:20:36:2C:B8:C6:2F:BF:19:6E:B0:
  • 6C:2B:79:0B:C4:1B:4E:AA:E4:06:F7:0A:8B:C8:5D:BB:
  • EF:8B:A9:06:FC:DA:AF
tlsfeature
  • status_request