SSL-Tools

SSL check results of mail.spirafix.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.spirafix.nl 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, 08 May 2024 20:52:27 +0000

The mailservers of mail.spirafix.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.spirafix.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spirafix.nl
91.107.237.77
 -
supported
spirafix.nl
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.spirafix.nl address so far. Test mail delivery

Certificates

First seen at:

CN=spirafix.nl

Certificate chain
  • spirafix.nl
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • spirafix.nl
Alternative Names
  • grond-ankers.nl
  • mail.spirafix.nl
  • spirafix.de
  • spirafix.es
  • spirafix.it
  • spirafix.nl
  • spirafix.pl
  • spirafix.ru
  • www.grond-ankers.nl
  • www.mail.spirafix.nl
  • www.spirafix.de
  • www.spirafix.es
  • www.spirafix.it
  • www.spirafix.nl
  • www.spirafix.pl
  • www.spirafix.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-08
Not valid after
2024-08-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F1:68:63:DC:BB:DF:ED:AB:8F:90:45:46:C2:5F:6B:B8:AD:6F:46:74:40:99:D2:D0:35:95:80:7E:33:89:72:6F
SHA1
93:96:02:36:96:84:54:89:26:F2:8D:E8:7C:A0:FB:2A:10:9E:61:A9
X509v3 extensions
subjectKeyIdentifier
  • 46:5A:A8:DA:04:8E:8B:C7:6B:B2:6F:4D:34:67:55:84:35:FC:58:1E
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 : 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 : May 8 20:22:50.217 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2F:65:22:14:FE:6D:17:BD:E3:D2:34:47:
  • 43:52:4E:1F:37:24:D8:6F:06:5F:C9:93:2B:14:79:C6:
  • 1F:ED:5D:73:02:20:0F:32:06:E8:FA:69:11:98:40:63:
  • 12:B8:3B:00:7C:1B:FC:7D:21:5C:3E:FF:11:11:49:7A:
  • 44:C4:EF:8A:A2: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 : May 8 20:22:50.320 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C1:FD:F1:10:92:26:7F:4F:83:54:FF:
  • 08:61:D6:A4:D7:03:8A:A0:AE:FF:4A:73:CE:6D:22:7E:
  • 9D:AA:51:95:C9:02:21:00:8F:09:B7:34:02:F0:35:AE:
  • 62:34:28:3C:C5:19:3B:CF:F0:CE:27:09:71:01:45:2D:
  • 0F:80:70:E0:37:42:6C:A1