SSL-Tools

SSL check results of ajuntamentdebenicarlo.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for ajuntamentdebenicarlo.org 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 Fri, 16 Apr 2021 07:37:59 +0000

The mailservers of ajuntamentdebenicarlo.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @ajuntamentdebenicarlo.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
srv1.benicarlo.org
185.133.96.19
 10
supported
srv1.benicarlo.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

We have received emails from these servers with @ajuntamentdebenicarlo.org sender addresses. Test mail delivery

Host TLS Version & Cipher
srv1.benicarlo.org (185.133.96.19)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=srv1.benicarlo.org

Certificate chain
  • srv1.benicarlo.org
    • 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)
  • srv1.benicarlo.org
Alternative Names
  • imap.ajuntamentdebenicarlo.org
  • imap.benicarlo.org
  • mail.ajuntamentdebenicarlo.org
  • mail.benicarlo.org
  • smtp.ajuntamentdebenicarlo.org
  • smtp.benicarlo.org
  • srv1.benicarlo.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-17
Not valid after
2021-06-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
77:20:C0:7B:4B:74:4D:37:96:B7:4A:BF:F1:BB:1B:93:02:38:9A:92:E3:B8:D9:30:DD:D8:7F:81:07:6E:48:A7
SHA1
E4:4B:86:04:48:5A:6D:44:5A:06:39:A9:AB:39:4C:AC:96:E9:D5:B9
X509v3 extensions
subjectKeyIdentifier
  • 24:22:67:CE:C6:CB:B8:8A:90:08:6B:A9:1E:EE:B6:30:47:00:68:5B
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 : Mar 17 07:44:13.297 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:76:A6:03:6D:50:2C:51:22:89:0C:C0:1F:
  • 2A:7C:28:C9:67:0B:B5:CE:73:AA:05:42:D4:B3:C7:FD:
  • 7B:C9:89:41:02:21:00:95:FC:1B:1D:DA:6E:79:1F:37:
  • D0:66:D1:74:DE:41:F1:64:7B:1D:C6:F0:6F:CD:B1:F6:
  • 60:B5:24:B3:4E:CA:A7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Mar 17 07:44:13.298 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4C:2D:F3:32:6C:7D:58:B3:8E:A6:47:01:
  • 5A:D1:4F:CF:C3:9E:DD:26:2C:34:1C:47:61:91:74:A0:
  • 8A:1A:B9:5D:02:21:00:EE:5B:B8:47:85:95:FB:B6:62:
  • D6:53:33:E5:5B:AD:AA:B1:0E:78:0F:6B:9F:F5:42:0C:
  • C5:15:51:7B:CE:77:28