SSL-Tools

SSL check results of nixe.fi

NEW You can also bulk check multiple servers.

Discover if the mail servers for nixe.fi 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, 22 Nov 2022 09:18:53 +0000

The mailservers of nixe.fi can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @nixe.fi addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.nixe.fi
91.159.216.24
 10
supported
*.nixe.fi
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
mx2.nixe.fi
185.53.129.182
Results incomplete
20
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mx3.nixe.fi
91.159.216.24
 30
supported
*.nixe.fi
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.nixe.fi

Certificate chain
  • *.nixe.fi
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.nixe.fi
Alternative Names
  • *.nixe.fi
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-10-31
Not valid after
2023-01-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C8:46:20:AD:09:2B:2F:65:6E:DF:5B:0A:11:C4:48:69:86:8D:4A:7B:FA:8D:02:97:1C:73:17:F1:5F:E3:48:21
SHA1
0E:46:F8:05:B0:FB:CF:54:68:C8:AB:86:F3:58:11:69:D5:CE:34:33
X509v3 extensions
subjectKeyIdentifier
  • 68:8D:A2:DE:17:62:67:7F:73:79:BE:32:20:56:1C:DD:E6:BD:95:43
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
  • 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 : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Oct 31 14:13:03.027 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:31:68:8C:59:E8:54:9F:9D:E3:5E:20:59:
  • DE:63:FA:CF:C5:7E:60:9F:95:0E:A6:FF:7A:22:87:B5:
  • 89:99:58:40:02:21:00:E1:7F:56:F6:76:0D:4B:69:DE:
  • AE:AF:2F:F5:4D:B8:31:08:DD:C7:21:19:B9:59:38:05:
  • 04:DE:59:AA:4D:73:70
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Oct 31 14:13:03.506 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:65:83:98:FB:FB:CD:89:83:33:F9:3B:38:
  • AD:27:FB:BE:1B:AD:E2:AF:8F:FD:CB:42:17:A7:5F:BA:
  • 23:E3:64:29:02:20:42:3C:0E:A7:D4:9A:44:3E:7B:BC:
  • 85:D4:27:91:BA:4B:10:68:66:50:4D:D0:ED:BE:F5:1E:
  • C8:8E:21:59:BA:A1