SSL-Tools

SSL check results of n0.lt

NEW You can also bulk check multiple servers.

Discover if the mail servers for n0.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 Sat, 06 Mar 2021 06:33:24 +0000

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

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

/mailservers/n0.lt

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.n0.lt
2a03:b0c0:2:d0::d1b:a001
Results incomplete
10
unsupported
not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx.n0.lt
188.166.32.32
 10
supported
n0.lt
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=n0.lt

Certificate chain
  • n0.lt
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • n0.lt
Alternative Names
  • *.n0.lt
  • n0.lt
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-19
Not valid after
2021-05-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8B:27:7B:DD:BF:6B:CB:0E:6D:45:89:CD:9A:99:1A:75:B4:04:3B:7E:24:30:EC:A4:A9:D0:6B:99:4B:00:45:D1
SHA1
1F:97:76:55:6C:CB:DF:0A:62:E7:14:82:2B:39:C4:D8:03:3A:67:DE
X509v3 extensions
subjectKeyIdentifier
  • CD:51:46:B9:FA:9B:29:94:BA:03:72:E9:36:95:2D:52:3B:84:E3:A6
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Feb 19 21:51:13.122 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6A:13:CF:10:C8:48:C0:27:9A:24:71:2F:
  • 72:2B:A7:50:9D:4E:22:A0:C3:DF:89:F5:65:2F:FF:71:
  • 5A:E1:98:57:02:20:16:7B:D8:14:A9:25:45:9B:46:B4:
  • 3E:B3:C3:56:43:AA:E2:6D:FD:C5:85:52:6E:F3:D9:E5:
  • 08:11:17:0D:34:D4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Feb 19 21:51:13.336 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:10:C9:3E:31:E0:1E:90:53:EA:97:0F:D4:
  • 28:BD:E2:B9:3C:4D:A5:12:DF:DF:9E:91:0E:26:A6:3A:
  • D5:F5:14:16:02:20:5D:18:47:8B:E3:62:50:85:CE:B3:
  • 63:AA:2D:18:83:2E:90:3E:B5:AD:1D:BE:96:81:F6:98:
  • 99:2C:59:45:B2:C9

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.mx.n0.lt
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mx.n0.lt
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
—
_25._tcp.mx.n0.lt
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
—
_25._tcp.mx.n0.lt
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
—
_25._tcp.mx.n0.lt
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mx.n0.lt
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
—