SSL-Tools

SSL check results of emedwards.info

NEW You can also bulk check multiple servers.

Discover if the mail servers for emedwards.info 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, 11 May 2021 18:05:32 +0000

No connection to the mailservers of emedwards.info could be established.

Servers

Incoming Mails

These servers are responsible for incoming mails to @emedwards.info addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.flighthost.xyz
2607:f740:16::e32
Results incomplete
10
supported
smtp.flighthost.xyz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
smtp.flighthost.xyz
192.73.242.212
Results incomplete
10
supported
smtp.flighthost.xyz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=smtp.flighthost.xyz

Certificate chain
  • smtp.flighthost.xyz
    • 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)
  • smtp.flighthost.xyz
Alternative Names
  • smtp.flighthost.xyz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-03
Not valid after
2021-07-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2D:4C:52:C1:3C:89:67:BF:23:DC:30:91:DA:B5:56:B6:FD:9F:FF:C9:D1:CB:C4:75:01:2B:1B:22:34:FA:AD:47
SHA1
CF:47:47:B9:C7:10:3D:FA:E2:43:08:AB:17:77:6C:A3:B4:A9:2F:0D
X509v3 extensions
subjectKeyIdentifier
  • BD:17:E6:E0:AD:B6:10:D7:28:56:9F:6B:FC:82:CA:16:A5:1D:C1:CB
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Apr 3 22:06:47.553 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7C:7A:79:2D:7E:F3:D2:28:99:9F:3A:B3:
  • 24:F8:88:CD:03:3A:4D:15:85:52:22:52:AB:09:69:7A:
  • B3:C6:6B:71:02:20:0D:58:49:FD:07:47:4A:23:8C:43:
  • 44:66:D4:62:74:92:D7:C8:14:16:DC:51:54:34:2B:0F:
  • 5F:F6:8C:A8:0D:C0
  • 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 3 22:06:47.603 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A2:C1:58:F3:2F:72:72:C2:3F:05:B8:
  • C4:1A:81:07:74:ED:97:5E:79:84:D2:10:33:D5:35:04:
  • 3F:90:54:62:CF:02:20:58:F0:83:6F:99:D6:BE:B8:38:
  • 6A:F5:A8:6A:E5:A6:A9:07:D2:2D:AE:F0:6C:9A:B0:F8:
  • 80:29:99:37:84:64:93