SSL-Tools

SSL check results of millertwain.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for millertwain.com 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 Thu, 23 Jan 2025 00:14:16 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.millertwain.com
2400:8907::f03c:95ff:fed4:55ff
 0
supported
mail.millertwain.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s
mail.millertwain.com
172.105.191.180
 0
supported
mail.millertwain.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.millertwain.com

Certificate chain
  • mail.millertwain.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.millertwain.com
Alternative Names
  • mail.millertwain.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-01-22
Not valid after
2025-04-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
14:B0:A1:A7:60:22:79:B2:7D:52:0E:62:05:2A:32:3D:81:54:FC:D3:1F:56:85:DB:1E:1E:74:24:EA:3C:B5:6B
SHA1
66:49:EB:C5:7F:5B:F8:56:B6:FF:73:60:6B:07:28:52:3C:67:E1:35
X509v3 extensions
subjectKeyIdentifier
  • B1:AD:C5:36:0D:29:43:67:CE:88:49:F4:F0:5F:FC:3D:6B:6F:97:19
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Jan 22 11:25:39.409 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CF:CB:2A:2F:0C:1C:E4:6C:DE:16:85:
  • E0:B1:DD:4E:47:D3:E8:7E:15:FC:A6:4C:B2:F9:C9:AC:
  • 9C:5F:9F:F8:E6:02:20:21:16:77:52:2A:9B:39:DF:E7:
  • FF:E8:39:8C:26:1F:F7:3B:8D:5C:9D:F5:CD:FB:AB:63:
  • A0:AA:AA:1F:9C:05:F8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 22 11:25:39.429 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5A:D8:64:80:3D:B7:37:B8:B6:28:F2:83:
  • A9:C0:E8:58:D7:84:3E:3F:C5:80:05:FF:8F:22:34:67:
  • BB:FA:75:07:02:20:2C:EE:6A:F2:61:2C:66:A3:DA:AF:
  • 88:EE:11:6D:04:23:FA:49:41:1E:57:F7:67:E0:42:78:
  • 51:30:94:00:71:1C