SSL-Tools

SSL check results of uromedicaldf.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for uromedicaldf.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, 15 Jan 2022 02:42:50 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.uromedicaldf.com.br
216.172.173.3
 0
supported
www.uromedical.cirurgiaroboticaembrasilia.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
42 s

Outgoing Mails

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

Certificates

First seen at:

CN=www.uromedical.cirurgiaroboticaembrasilia.com.br

Certificate chain
Subject
Common Name (CN)
  • www.uromedical.cirurgiaroboticaembrasilia.com.br
Alternative Names
  • *.cirurgiaroboticaembrasilia.com.br
  • *.drdiogomendes.com.br
  • *.uroinstituto.com.br
  • *.uromedical.com.br
  • *.uromedicaldf.com.br
  • cirurgiaroboticaembrasilia.com.br
  • drdiogomendes.com.br
  • uroinstituto.com.br
  • uromedical.com.br
  • uromedicaldf.com.br
  • www.drdiogomendes.cirurgiaroboticaembrasilia.com.br
  • www.uromedical.cirurgiaroboticaembrasilia.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-11-28
Not valid after
2022-02-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
0E:09:D4:63:B7:FF:CC:B4:12:A7:23:82:16:DE:C5:62:8B:25:FF:6A:EF:20:40:CF:A3:01:3C:43:7D:EA:78:EE
SHA1
E7:D4:1A:D0:9E:23:A2:57:39:D4:61:80:9F:1E:C3:F1:B8:16:FE:A4
X509v3 extensions
subjectKeyIdentifier
  • C0:A6:E7:A0:87:91:1C:04:80:FD:BA:8C:31:52:CC:11:50:CC:22:5F
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 : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
  • 4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
  • Timestamp : Nov 28 04:19:03.735 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7C:71:4A:0B:D5:3C:8A:79:AD:B9:E3:9A:
  • 94:E7:9E:BA:FA:19:AC:FC:69:61:35:92:3E:4A:02:AA:
  • FC:5A:66:D1:02:21:00:AE:F6:2A:E5:F2:B1:AB:9C:DC:
  • E4:26:9D:2E:A5:5E:C3:78:FE:E2:8F:A6:72:4D:7E:C9:
  • A1:1B:10:58:AD:E6:90
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Nov 28 04:19:03.742 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:80:C9:A2:99:4E:91:B7:70:53:7B:1F:
  • 91:A9:88:B6:0E:E2:F0:6B:7B:54:3D:F0:E4:1A:12:92:
  • D2:D7:12:32:E1:02:20:57:D3:8C:C4:FD:78:BB:9A:76:
  • C0:6B:E6:6E:EC:33:16:E8:2B:E6:9D:1C:BA:3A:19:D1:
  • A1:BB:E6:CB:03:4D:72