SSL-Tools

SSL check results of yawl.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for yawl.com.br 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, 18 Jul 2020 01:29:24 +0000

The mailservers of yawl.com.br can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.yawl.com.br
186.251.241.237
 10
supported
yawl.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
22 s

Outgoing Mails

We have received emails from these servers with @yawl.com.br sender addresses. Test mail delivery

Host TLS Version & Cipher
unknown (186.251.247.58)
Insecure - not encrypted!

Certificates

First seen at:

CN=yawl.com.br

Certificate chain
Subject
Common Name (CN)
  • yawl.com.br
Alternative Names
  • *.yawl.com.br
  • yawl.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-06-27
Not valid after
2020-09-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
00:06:AC:BD:69:19:50:7C:A7:BB:DF:08:0E:BD:DA:F4:15:EA:D1:E1:35:35:7D:23:CA:86:AE:7D:34:1A:12:8C
SHA1
2A:DF:E3:D5:22:25:CF:70:99:E6:BA:2D:FA:D7:DC:81:74:53:70:61
X509v3 extensions
subjectKeyIdentifier
  • 5F:C0:51:A9:26:B0:B0:33:16:97:A6:3D:25:00:00:8A:D2:7C:92:65
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Jun 27 16:37:15.471 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C2:E2:31:41:E9:66:FF:A8:30:E3:A1:
  • 46:95:66:D7:43:F5:A1:BF:0D:A6:87:D0:F2:AD:1F:39:
  • EB:60:36:9F:9E:02:20:5D:6A:80:72:5E:53:FC:90:C3:
  • 63:AE:AC:E3:36:C9:9F:E7:AA:0B:A5:24:24:30:1B:67:
  • 6E:D7:98:4F:01:AE:A9
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jun 27 16:37:15.524 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A0:13:30:2F:54:4B:F2:31:E0:FB:5E:
  • 00:D4:3F:9F:E5:DF:82:00:44:7B:C8:14:58:35:0A:4A:
  • 11:D2:0E:BA:5E:02:21:00:A2:7A:C3:A7:8D:A0:60:59:
  • E8:F2:14:66:E2:B7:97:EA:72:19:97:EE:95:E4:C0:8E:
  • 02:35:16:5B:D7:BE:FB:73