SSL-Tools

SSL check results of villalexingtonbeach.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for villalexingtonbeach.com 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 Tue, 07 May 2024 11:08:05 +0000

We can not guarantee a secure connection to the mailservers of villalexingtonbeach.com!

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

/mailservers/villalexingtonbeach.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @villalexingtonbeach.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.villalexingtonbeach.com
2001:a61:2558:c01:f464:d792:24ef:897b
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
smtp.villalexingtonbeach.com
93.104.68.129
 10
supported
villalexingtonbeach.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=villalexingtonbeach.com

Certificate chain
  • villalexingtonbeach.com
    • remaining
    • 2048 bit
    • sha384WithRSAEncryption
    • Hostname Mismatch
    • Unknown Authority
      ZeroSSL RSA Domain Secure Site CA
Subject
Common Name (CN)
  • villalexingtonbeach.com
Alternative Names
  • villalexingtonbeach.com
  • www.villalexingtonbeach.com
Issuer
Country (C)
  • AT
Organization (O)
  • ZeroSSL
Common Name (CN)
  • ZeroSSL RSA Domain Secure Site CA
validity period
Not valid before
2024-05-06
Not valid after
2024-08-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5D:A5:04:36:8A:23:64:24:84:A1:EB:CC:CA:EE:74:03:9E:EC:AA:A4:4D:5A:D5:40:66:D4:89:A0:10:E1:C3:20
SHA1
02:72:D6:EC:BC:94:71:64:8F:F8:05:99:CD:6F:D3:3A:9C:3A:1D:47
X509v3 extensions
authorityKeyIdentifier
  • keyid:C8:D9:78:68:A2:D9:19:68:D5:3D:72:DE:5F:0A:3E:DC:B5:86:86:A6
subjectKeyIdentifier
  • 89:2E:A9:0D:44:CF:B2:4F:39:59:1F:1A:F8:F9:2F:04:4E:22:89:E7
certificatePolicies
  • Policy: 1.3.6.1.4.1.6449.1.2.2.78
  • CPS: https://sectigo.com/CPS
  • Policy: 2.23.140.1.2.1
authorityInfoAccess
  • CA Issuers - URI:http://zerossl.crt.sectigo.com/ZeroSSLRSADomainSecureSiteCA.crt
  • OCSP - URI:http://zerossl.ocsp.sectigo.com
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : May 6 05:08:03.569 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2F:6B:5D:F1:FB:0B:68:1C:D2:7B:57:CB:
  • 3A:B9:CA:23:92:73:1C:EB:3F:52:8A:A8:79:38:FA:65:
  • 34:CF:50:39:02:21:00:A4:27:83:25:B2:EC:7B:7B:69:
  • B0:43:E2:27:FD:A2:2E:E4:20:0D:77:16:A0:E6:85:43:
  • 86:BD:D4:3C:5B:B5:3C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : May 6 05:08:03.513 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FA:0B:00:70:F2:48:D7:91:B9:57:51:
  • 2D:C3:46:29:89:E8:9E:06:09:D8:89:90:B4:D9:8C:3F:
  • 14:19:2D:1D:75:02:21:00:EA:A7:C4:FB:A2:5E:DF:E3:
  • 19:52:4D:11:6C:A9:D9:B3:B5:61:4D:F7:EF:C8:39:CF:
  • 67:69:7F:C8:7F:DE:0A:65