SSL-Tools

SSL check results of byte.wtf

NEW You can also bulk check multiple servers.

Discover if the mail servers for byte.wtf 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 Fri, 16 Apr 2021 08:16:54 +0000

The mailservers of byte.wtf can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @byte.wtf addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.byteturtle.eu
2a01:4f8:1c1c:939::1
 10
supported
mail.byteturtle.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s
mail.byteturtle.eu
195.201.129.13
 10
supported
mail.byteturtle.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.byteturtle.eu

Certificate chain
  • mail.byteturtle.eu
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • mail.byteturtle.eu
Alternative Names
  • autodiscover.pantsu.biz
  • mail.byteturtle.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-15
Not valid after
2021-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
12:1C:7A:4A:C1:C5:7E:A7:4A:96:6D:2E:32:A1:EE:64:5C:DA:7F:CC:29:CC:45:8E:26:A0:F1:7E:89:AC:4F:EE
SHA1
28:6D:6B:5F:CA:1A:E7:DB:8D:3F:BD:2D:41:BE:BD:2B:68:0A:D1:7C
X509v3 extensions
subjectKeyIdentifier
  • 8C:00:C1:36:4A:15:8E:87:32:D5:72:37:19:B9:C3:DE:FD:AC:DA:92
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Apr 15 22:06:25.506 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BA:1F:E8:95:47:06:71:97:6E:87:E0:
  • 7E:78:C4:78:34:2B:15:FD:23:E4:E4:24:51:D0:3D:E4:
  • 86:26:BA:ED:2D:02:20:03:32:98:AA:8A:EF:F2:4D:7B:
  • CC:E9:8B:D6:BA:9C:A5:E1:10:BC:34:99:59:E3:92:6A:
  • 23:9B:D1:37:C9:48:1B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Apr 15 22:06:25.509 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:29:34:6C:87:22:EE:73:04:A7:70:69:01:
  • C9:DC:B7:D7:19:5C:59:B7:7D:04:C9:D9:02:5E:BB:CE:
  • DE:9E:3D:66:02:20:5F:41:AD:9F:92:05:8E:B4:C0:49:
  • C6:2B:37:34:81:C3:89:EA:B2:EF:7D:8B:0A:A4:16:6B:
  • 55:07:E2:2F:58:B1