SSL-Tools

SSL check results of gama.serv.lt

NEW You can also bulk check multiple servers.

Discover if the mail servers for gama.serv.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 Mon, 25 Mar 2024 19:41:26 +0000

We can not guarantee a secure connection to the mailservers of gama.serv.lt!

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

/mailservers/gama.serv.lt

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.gama.serv.lt
2001:41d0:d:2f53:1c0::41
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx.gama.serv.lt
178.33.220.205
 10
supported
gama.serv.lt
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @gama.serv.lt address so far. Test mail delivery

Certificates

First seen at:

CN=gama.serv.lt

Certificate chain
  • gama.serv.lt
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • gama.serv.lt
Alternative Names
  • gama.serv.lt
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-01-30
Not valid after
2024-04-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
33:05:E3:88:AD:68:FD:62:12:01:46:5D:49:85:F8:AD:ED:F0:9D:B1:1E:C0:11:40:63:0B:07:5D:C0:3F:C4:47
SHA1
88:02:47:2D:8F:D1:40:E3:FA:F0:26:FE:46:14:91:05:B2:CD:0C:12
X509v3 extensions
subjectKeyIdentifier
  • 9E:28:46:AD:F1:60:76:26:BC:53:87:D5:71:EC:B8:77:48:BA:22:16
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 : Jan 30 22:11:29.515 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1A:D2:02:1C:E5:0C:F6:96:30:47:55:7E:
  • 1E:C7:7A:8A:55:A3:6B:21:A6:0C:6B:C5:24:B7:74:BB:
  • 8F:C0:3C:40:02:20:12:D2:D2:5D:53:62:A3:42:16:5C:
  • 3B:59:62:70:A3:7A:BE:15:14:96:1E:56:26:CC:43:F4:
  • 93:03:0B:64:D1:D8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Jan 30 22:11:29.506 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CB:A6:3B:A1:98:6B:8A:D0:4E:FD:3F:
  • F7:83:42:11:15:39:E7:A8:E1:F3:49:8E:DF:5F:64:B7:
  • 9F:4E:44:F7:BF:02:20:55:97:7F:5F:3E:10:2B:E2:73:
  • 1F:5F:BB:B9:3F:B1:35:1C:B9:13:03:36:14:2A:A7:F5:
  • 84:7F:A1:C5:3C:3E:37