SSL-Tools

SSL check results of mikkonen.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mikkonen.com 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, 15 May 2024 16:19:07 +0000

The mailservers of mikkonen.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mikkonen.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
gaebolg.hexmodeus.com
2a04:3540:1000:310:d01e:6bff:fe4e:961
 0
supported
gaebolg.hexmodeus.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
gaebolg.hexmodeus.com
94.237.37.123
 0
supported
gaebolg.hexmodeus.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=gaebolg.hexmodeus.com

Certificate chain
  • gaebolg.hexmodeus.com
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • gaebolg.hexmodeus.com
Alternative Names
  • gaebolg.hexmodeus.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-11
Not valid after
2024-08-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8F:0F:25:F6:21:7C:C6:A8:B0:12:AC:5D:DC:92:BA:CE:16:23:CC:D3:EE:C9:8D:0D:41:78:FD:22:BC:61:1F:15
SHA1
50:DA:3E:EE:2E:FB:48:EE:ED:AD:30:A3:27:0C:17:15:6B:52:0B:4E
X509v3 extensions
subjectKeyIdentifier
  • 81:6E:4B:DF:84:1D:A6:54:B1:E4:D1:10:53:70:50:3E:D5:8B:1F:38
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 : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : May 11 08:05:48.768 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:27:C6:99:55:17:23:85:98:B5:15:D1:27:
  • 3C:EC:0A:69:40:06:9D:AA:62:06:B5:A8:AD:D4:46:8D:
  • 81:15:16:9C:02:20:2D:7B:C4:26:45:8E:B4:96:F3:A9:
  • 54:38:05:DE:B6:78:61:ED:83:F0:16:54:78:4E:C8:CA:
  • 99:43:A6:AA:0D:6E
  • 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 : May 11 08:05:48.827 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3A:4E:BC:41:3E:CE:94:E3:05:BC:74:AC:
  • 82:D1:F9:29:16:4C:AE:BD:A4:15:40:33:33:66:26:44:
  • 98:27:5C:9A:02:21:00:C3:F3:39:EF:13:7F:6D:3F:27:
  • 3C:75:D3:D6:4E:BB:C8:22:74:3F:04:F5:9E:A2:3B:4A:
  • 50:09:37:B8:59:1C:C2