SSL-Tools

SSL check results of einmo.no

NEW You can also bulk check multiple servers.

Discover if the mail servers for einmo.no 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, 16 Sep 2024 11:02:45 +0000

The mailservers of einmo.no can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @einmo.no addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
einmo.no
109.247.192.116
 0
supported
einmo.no
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=einmo.no

Certificate chain
  • einmo.no
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • einmo.no
Alternative Names
  • *.einmo.no
  • einmo.no
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-07-29
Not valid after
2024-10-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
64:A8:73:F5:9E:8D:CC:8E:EC:27:7E:6F:5E:0D:6C:67:ED:5C:AD:05:20:82:5C:D6:CD:B8:DE:94:01:8E:F1:65
SHA1
D9:90:7A:BD:BF:DA:90:F1:13:80:9B:A3:92:86:CA:1E:39:D8:95:4A
X509v3 extensions
subjectKeyIdentifier
  • 3E:75:75:E5:EF:A0:4E:A5:A1:D1:10:72:79:D6:D0:B6:F5:C1:5B:F8
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Jul 29 04:38:12.240 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:60:5D:AB:DE:15:2A:A7:77:FC:5A:A1:23:
  • B2:BB:01:19:9F:73:83:EE:C4:38:0C:BB:85:F3:0C:11:
  • 28:70:56:CE:02:20:1F:BC:D4:2F:27:D0:AF:29:7D:19:
  • E2:E0:DF:F7:C3:13:14:0B:F8:0E:90:7E:49:F7:52:B5:
  • 9A:E5:75:CD:C9:2A
  • 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 : Jul 29 04:38:12.236 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AD:48:76:75:73:15:DF:8B:9B:54:00:
  • 14:CA:8D:10:42:A3:1F:BA:B8:8E:05:49:24:DD:3E:AF:
  • A4:13:D3:CF:52:02:20:4B:F1:E1:B0:8E:63:0E:74:7D:
  • 1C:EC:07:07:40:04:24:3D:DC:F6:A6:FC:3F:DF:E8:F6:
  • C6:AD:CA:D8:52:DE:AB