SSL-Tools

SSL check results of mail.hitmare.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.hitmare.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 Tue, 01 Oct 2024 21:10:14 +0000

The mailservers of mail.hitmare.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.hitmare.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.hitmare.net
136.243.78.121
 -
supported
mail.hitmare.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.hitmare.net
2a01:4f8:212:2c44::f121
 -
supported
mail.hitmare.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.hitmare.net

Certificate chain
  • mail.hitmare.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.hitmare.net
Alternative Names
  • mail.hitmare.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-16
Not valid after
2024-12-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DD:C0:3B:7C:E1:55:14:3E:4F:08:CB:27:7D:15:CC:97:31:AA:B0:F3:FF:94:62:6F:C4:21:F7:5A:33:C7:0D:B8
SHA1
56:7B:CF:CA:FF:C2:23:06:54:8B:78:56:A0:54:EF:F8:B2:D7:C9:38
X509v3 extensions
subjectKeyIdentifier
  • FD:5C:50:5B:4E:7D:BE:4E:13:7D:0D:BA:EF:C3:25:FD:38:8A:3B:F9
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 : Sep 16 07:01:50.625 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:27:6D:73:08:77:08:AC:18:32:86:C9:05:
  • 70:82:F2:D3:20:93:56:23:F3:50:54:D5:38:18:CF:96:
  • C0:A9:A6:B0:02:21:00:F5:15:96:54:31:8B:BD:6E:C3:
  • 49:10:3F:77:99:51:C8:5F:7B:A5:08:13:0A:22:37:58:
  • 1D:A7:B3:CC:B3:E7:BB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Sep 16 07:01:50.794 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7B:8F:EA:18:A3:FE:B3:89:34:21:11:A7:
  • 93:F1:39:B1:16:5E:18:24:92:49:30:1B:8F:30:A3:B5:
  • 1E:E9:BD:EC:02:20:3D:37:75:C7:F3:97:D2:15:61:43:
  • 4B:23:31:AA:E0:24:3F:49:09:B7:93:49:6D:ED:9E:2E:
  • 8C:C5:4B:2B:C1:BF