SSL check results of williambr.uno

NEW You can also bulk check multiple servers.

Discover if the mail servers for williambr.uno 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 Tue, 15 Jun 2021 04:35:34 +0000

The mailservers of williambr.uno can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @williambr.uno addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.williambr.uno
2607:5501:3000:805::2
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
mail.williambr.uno
104.168.149.28
10
supported
mail.danartnyc.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
26 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.danartnyc.com

Certificate chain
  • mail.danartnyc.com
    • 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.danartnyc.com
Alternative Names
  • mail.danartnyc.com
  • mail.markfamor.com
  • mail.rawfuc.kr
  • mail.rawfuck.me
  • mail.williambr.uno
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-06
Not valid after
2021-07-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
89:31:24:4C:BF:C0:43:76:CD:9C:88:EB:8A:D9:CB:26:AB:E0:1D:F3:5E:82:F7:9C:E7:A2:4C:03:A3:F0:07:86
SHA1
70:D8:A1:39:47:0C:69:E9:47:A7:75:E1:09:93:4A:D2:9A:79:18:23
X509v3 extensions
subjectKeyIdentifier
  • 64:2C:49:56:EE:B5:9A:83:D4:0E:82:A5:C8:50:D5:07:C9:CC:CD:BB
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 : 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 : Apr 6 15:24:27.651 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CE:EF:B4:B0:8A:B6:16:10:02:64:69:
  • 06:0A:25:32:6D:F9:C8:1F:56:12:AC:86:A7:19:94:A9:
  • 95:27:EF:2C:9A:02:21:00:FE:39:50:12:F6:3C:D3:02:
  • DD:3E:E3:D7:FA:B2:8E:9A:8E:61:5A:89:AD:3D:18:31:
  • BA:BE:50:30:DC:85:B3:EC
  • 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 : Apr 6 15:24:27.646 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5D:7E:D3:CD:60:2A:91:E4:C0:1E:93:1F:
  • 68:9F:BB:AB:1B:E1:D3:2A:11:22:5D:2F:C6:A9:92:74:
  • D6:E1:8A:FB:02:20:23:CC:00:0F:AF:78:95:96:BE:45:
  • 4E:B1:CE:82:E1:2B:78:D2:5A:97:B5:A6:BF:19:69:83:
  • 0B:80:2A:56:AB:47