SSL check results of doom.sfat.host

NEW You can also bulk check multiple servers.

Discover if the mail servers for doom.sfat.host 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 Fri, 04 Oct 2024 01:54:08 +0000

The mailservers of doom.sfat.host can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @doom.sfat.host addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
doom.sfat.host
65.108.77.232
-
supported
doom.sfat.host
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
doom.sfat.host
2a01:4f9:6b:2548::2
-
supported
doom.sfat.host
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @doom.sfat.host address so far. Test mail delivery

Certificates

First seen at:

CN=doom.sfat.host

Certificate chain
  • doom.sfat.host
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • doom.sfat.host
Alternative Names
  • doom.sfat.host
  • mail.sfatllc.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-03
Not valid after
2024-12-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
95:3B:26:C9:E3:F4:1F:02:A9:0A:C0:CF:9A:4C:95:C8:40:F8:64:87:0E:55:64:28:05:0B:34:87:79:CE:76:63
SHA1
9C:54:E6:7A:90:E6:C1:0A:92:C0:E2:8F:4F:FC:7E:B8:12:FC:49:28
X509v3 extensions
subjectKeyIdentifier
  • 2D:29:01:A7:67:29:F3:C5:EC:03:C9:27:0E:4C:B5:C2:E5:45:0D:9C
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 3 14:26:45.837 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5C:69:43:2A:73:40:41:25:83:36:BB:E9:
  • 5E:5B:7F:55:06:4F:C9:D8:57:A1:53:68:01:A2:E8:3E:
  • 55:39:54:82:02:20:68:40:01:68:E0:63:DB:C2:1D:95:
  • CD:80:92:87:A1:F6:6C:2B:6E:2E:05:9E:82:06:EA:11:
  • C9:15:5D:E5:4D:48
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Sep 3 14:26:45.900 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5F:05:0B:4F:9A:22:13:26:5C:58:00:3E:
  • 97:EE:E1:2F:92:06:F3:E6:16:D1:A5:91:D8:A4:F8:85:
  • CD:52:D7:FD:02:20:54:F1:60:88:0E:31:1B:EE:04:7D:
  • F7:B0:AE:86:7A:B1:50:99:E5:2F:E1:36:AF:36:63:B7:
  • C2:DE:20:E6:E0:0E

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.doom.sfat.host
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid