SSL-Tools

SSL check results of vaikes.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for vaikes.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, 22 Oct 2024 00:30:38 +0000

We can not guarantee a secure connection to the mailservers of vaikes.net!

Please contact the operator of vaikes.net and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/vaikes.net

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.vaikes.net
2a01:239:270:1d00::1
Results incomplete
0
unsupported
not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.vaikes.net
85.215.132.16
 0
supported
mail.vaikes.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.vaikes.net

Certificate chain
  • mail.vaikes.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.vaikes.net
Alternative Names
  • mail.vaikes.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-19
Not valid after
2025-01-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
72:B5:37:6D:3F:27:25:76:4D:03:E0:C7:68:4E:88:27:6C:5E:19:81:30:94:1B:B3:C8:EF:D4:97:3F:35:70:2F
SHA1
D0:8A:0E:A1:4F:41:16:C6:41:1C:17:31:EE:6D:D0:53:00:96:07:30
X509v3 extensions
subjectKeyIdentifier
  • DD:B2:C4:DC:F3:B9:8F:8A:FF:09:E7:6C:A3:15:25:29:D5:9A:4D:05
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 : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 19 18:18:23.160 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F5:59:97:4A:BE:58:37:EA:A4:99:4A:
  • 2D:39:8C:9E:92:F8:17:FD:96:94:5B:4C:54:61:80:4C:
  • 75:1C:21:94:10:02:20:50:99:49:DC:7A:79:6C:9D:F3:
  • FD:4D:38:79:86:5E:4A:8A:AC:D3:40:25:29:8A:31:4C:
  • 9E:A8:A3:30:0F:0C:04
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Oct 19 18:18:23.324 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:82:5F:BA:4B:24:5C:70:78:E0:24:55:
  • 40:5E:30:E0:EC:20:0C:E0:B3:DA:C8:38:40:B2:28:D8:
  • 56:30:F6:D7:5F:02:20:0B:2E:DF:BD:31:5D:DD:F3:C5:
  • A7:B8:6B:8B:EC:A6:C8:97:4C:05:F7:83:1C:83:93:87:
  • 72:67:8C:C3:AE:6C:DA

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.vaikes.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid