SSL-Tools

SSL check results of ilva.lv

NEW You can also bulk check multiple servers.

Discover if the mail servers for ilva.lv 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 Thu, 07 Dec 2023 09:03:56 +0000

We can not guarantee a secure connection to the mailservers of ilva.lv!

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

/mailservers/ilva.lv

Servers

Incoming Mails

These servers are responsible for incoming mails to @ilva.lv addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.ilva.lv
80.233.228.20
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail2.ilva.lv
2001:41d0:701:1100::230a
Results incomplete
30 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail2.ilva.lv
162.19.224.132
 30
supported
mail2.ilva.lv
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 @ilva.lv address so far. Test mail delivery

Certificates

First seen at:

CN=mail2.ilva.lv

Certificate chain
  • mail2.ilva.lv
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Unknown Authority
      R3
Subject
Common Name (CN)
  • mail2.ilva.lv
Alternative Names
  • mail2.ilva.lv
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-09-30
Not valid after
2023-12-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B3:A8:5C:81:A4:7A:34:5A:12:6C:E2:D9:58:79:24:3C:C3:02:03:D3:C5:CB:CF:C1:70:E9:51:05:16:E8:AB:76
SHA1
93:01:14:31:D1:DA:F4:0B:47:13:20:E0:5A:49:D3:73:F3:43:F9:C9
X509v3 extensions
subjectKeyIdentifier
  • 94:41:24:0C:DC:CE:E6:83:5E:55:8B:AB:50:A4:46:E4:C0:BC:B4:03
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 : 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 1 00:55:12.934 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:55:AB:8F:04:9A:72:46:2A:25:BC:5E:AA:
  • 09:82:A7:0D:CE:6E:06:42:11:A8:ED:CA:2F:B0:44:F4:
  • 2E:C5:22:C6:02:20:3D:23:D2:60:59:55:B5:1A:67:5B:
  • 4D:30:E0:01:27:BC:40:C5:62:32:15:1F:E4:A8:CD:CD:
  • 66:DC:34:76:4A:BF
  • 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 1 00:55:12.937 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6E:C3:6F:CC:C5:80:8F:48:4D:76:06:9A:
  • 17:8F:9F:4E:BB:D9:F4:38:0E:4D:00:C8:DA:BB:9E:7E:
  • DE:1A:45:2B:02:21:00:A5:EB:B9:F1:6C:B8:5C:BF:53:
  • 15:25:B3:47:F1:A6:5E:14:D3:53:4E:D3:BC:D6:C3:F3:
  • 71:CF:A3:0D:A9:E2:04