SSL-Tools

SSL check results of gravera.lt

NEW You can also bulk check multiple servers.

Discover if the mail servers for gravera.lt 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, 17 Nov 2022 15:49:58 +0000

The mailservers of gravera.lt can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @gravera.lt addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
wave.gravera.lt
217.9.252.69
 10
supported
*.gravera.lt
DANE
missing
PFS
unsupported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.0
  • SSLv3
2 s
banga.gravera.lt
82.140.133.141
 20
supported
*.gravera.lt
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @gravera.lt sender addresses. Test mail delivery

Host TLS Version & Cipher
banga.gravera.lt (82.140.133.141)
TLSv1 ECDHE-RSA-AES256-SHA

Certificates

First seen at:

CN=*.gravera.lt

Certificate chain
  • *.gravera.lt
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.gravera.lt
Alternative Names
  • *.gravera.lt
  • gravera.lt
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-11-15
Not valid after
2023-02-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A9:B2:EE:86:D8:05:3B:17:14:A5:28:D6:52:F6:D9:D1:79:DB:B1:14:2E:03:FD:19:D5:8A:6D:F0:22:3B:F4:61
SHA1
91:48:3D:A0:94:34:C9:68:82:F4:83:6B:2D:87:AA:B6:56:64:95:61
X509v3 extensions
subjectKeyIdentifier
  • 36:FD:BE:88:CA:9F:AD:6D:E1:66:DD:DE:54:DF:21:30:B4:CF:00:9E
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 : Nov 15 21:29:11.500 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:DD:EE:17:BF:CD:66:83:ED:41:40:B4:
  • A0:18:B7:C3:07:B5:5A:D7:CA:93:E7:F9:3D:B0:CD:3D:
  • 28:C2:94:FE:9D:02:21:00:D5:64:DC:C2:05:49:BA:3B:
  • 69:4A:B1:86:9A:1B:C4:A0:42:F4:AA:9E:EC:C6:ED:9B:
  • 18:CF:1E:92:57:04:F9:93
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
  • 03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
  • Timestamp : Nov 15 21:29:11.466 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:89:9D:D0:4F:8C:7F:DF:15:F4:65:9E:
  • 4A:BB:F2:52:63:8B:0F:B4:93:51:AF:C4:37:22:D7:3F:
  • 4F:81:26:AB:4D:02:21:00:FA:43:3F:40:DB:71:05:0C:
  • 30:A7:33:47:57:12:E5:8A:67:B7:83:01:EF:9F:C2:20:
  • 02:B9:EF:0B:9B:FF:26:E1