SSL-Tools

SSL check results of gkeller.info

NEW You can also bulk check multiple servers.

Discover if the mail servers for gkeller.info 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 Mon, 15 Apr 2024 06:19:00 +0000

We can not guarantee a secure connection to the mailservers of gkeller.info!

Please contact the operator of gkeller.info and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/gkeller.info

Servers

Incoming Mails

These servers are responsible for incoming mails to @gkeller.info addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.gkeller.info
2a0d:5940:7:b6::b753
Results incomplete
10
unsupported
not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
2 s
mail.gkeller.info
2.59.133.90
 10
supported
mail.gkeller.info
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.gkeller.info

Certificate chain
  • mail.gkeller.info
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.gkeller.info
Alternative Names
  • mail.gkeller.info
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-18
Not valid after
2024-06-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
0B:CC:F6:4C:E6:11:3B:D5:E5:FC:FC:38:38:4B:F8:9F:83:6F:D7:DB:07:1B:5E:13:E6:DE:F1:66:97:8F:27:33
SHA1
37:2E:4A:1F:57:0C:E0:16:7F:CB:31:A1:CE:F6:6B:C9:2B:45:DA:3F
X509v3 extensions
subjectKeyIdentifier
  • D3:EF:D4:73:28:CC:CC:5C:60:08:FA:7E:DB:2E:48:7F:99:B6:8E:B7
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 18 02:02:45.389 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FE:5B:D6:32:8C:81:BC:8D:D4:67:F0:
  • 65:82:50:AF:C9:1D:B4:43:1D:D8:66:F3:71:91:6C:2F:
  • FC:F0:F0:BD:6B:02:20:1B:AC:29:75:45:D3:50:2F:07:
  • 24:20:B0:38:27:92:6A:44:D6:00:5B:56:D5:45:B0:4E:
  • C7:50:FE:AA:C2:DC:6F
  • 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 : Mar 18 02:02:45.409 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B5:00:56:39:27:05:A9:A5:F0:FF:B1:
  • 22:38:AD:D7:9B:D1:D0:10:3B:9B:48:CC:B3:7A:89:A5:
  • 61:F8:1B:6B:1C:02:20:3B:CA:0B:67:C0:91:26:B1:F9:
  • BC:E1:E2:E9:2F:38:68:1F:C9:0D:CB:6A:4C:19:3C:91:
  • C4:47:90:47:BD:AD:01

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.gkeller.info
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid