SSL check results of vaccarelli.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for vaccarelli.net 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

Report created Fri, 05 Mar 2021 22:04:24 +0000

The mailservers of vaccarelli.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @vaccarelli.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.vaccarelli.net
2a03:b0c0:2:d0::fad:e001
1
supported
mail.vaccarelli.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.vaccarelli.net
68.183.12.59
1
supported
mail.vaccarelli.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @vaccarelli.net sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.vaccarelli.net (68.183.12.59)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.vaccarelli.net

Certificate chain
  • mail.vaccarelli.net
    • 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)
  • mail.vaccarelli.net
Alternative Names
  • mail.vaccarelli.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-05
Not valid after
2021-06-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
73:FC:0F:D3:20:29:21:55:40:07:68:1C:46:C3:C2:E6:F0:5D:0B:AA:F2:56:1B:26:B7:35:55:3F:31:60:84:0B
SHA1
B1:51:38:9A:F8:61:06:09:D7:8A:9B:6E:3D:92:E4:19:FC:87:5E:58
X509v3 extensions
subjectKeyIdentifier
  • 69:AC:EB:82:91:97:77:67:84:D3:FA:9A:00:53:BA:96:7F:C1:2E: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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Mar 5 17:25:51.795 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F5:58:29:4D:2B:2D:E4:74:9C:60:A9:
  • 93:FB:B8:E6:E0:11:05:C9:40:6D:CB:C4:04:54:DB:DB:
  • DF:07:B3:A9:F0:02:20:3E:68:8A:FD:E0:B4:1F:FD:E2:
  • 06:F6:3C:2D:81:CF:E2:43:7B:32:5D:BE:6E:06:6C:36:
  • DC:8F:D1:9C:0A:0A:E2
  • 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 : Mar 5 17:25:51.888 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0D:FE:48:82:06:4A:FB:67:FC:73:E8:A6:
  • F3:72:9A:77:3B:98:0D:BA:C2:34:6A:88:A7:47:12:46:
  • 8E:B0:56:FB:02:20:03:7B:03:65:87:75:B7:85:77:A4:
  • 01:63:6C:0D:F0:6D:83:34:F0:97:62:32:7C:7A:64:0F:
  • 57:1C:28:E6:F8:51