SSL-Tools

SSL check results of swill.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for swill.org 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, 10 Jan 2025 20:26:24 +0000

The mailservers of swill.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @swill.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.swill.org
2a02:169:f403::80e4:e0ff:fe00:4092
 10
supported
mail.swill.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.swill.org
77.74.84.189
 10
supported
mail.swill.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.swill.org

Certificate chain
  • mail.swill.org
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.swill.org
Alternative Names
  • mail.swill.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-12-15
Not valid after
2025-03-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
41:EF:6C:FD:AF:1E:7E:AC:5E:9F:14:C2:D6:1C:89:12:03:76:CF:EF:F5:73:E9:A1:C7:A3:8A:72:15:0A:85:4E
SHA1
C8:4A:15:29:0C:9A:DB:E4:01:39:BC:9D:25:76:DB:D6:29:C6:B7:D0
X509v3 extensions
subjectKeyIdentifier
  • 6F:EB:58:70:DD:07:BB:F9:EC:D1:0B:F5:0C:89:F8:7A:AA:D2:A8:36
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 : 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 : Dec 15 17:59:48.591 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:38:B7:A0:E7:22:47:8F:6F:77:5A:BA:EF:
  • 21:AC:7E:9D:17:1E:59:2D:AD:B5:10:66:57:6B:FE:EE:
  • 29:F4:5B:0A:02:21:00:EE:6F:63:52:93:AC:C0:D1:5E:
  • 35:1D:0F:7E:58:BC:84:4D:93:59:53:20:33:13:10:07:
  • 68:8C:24:C9:6E:14:BA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Dec 15 17:59:48.628 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CA:01:5F:74:E6:F6:C2:CC:E6:C6:F2:
  • 98:E4:F8:A7:4D:F0:25:11:73:AC:57:17:FB:EA:08:5E:
  • 10:23:E8:05:56:02:21:00:A5:5A:AD:D0:4D:3B:BB:2A:
  • B9:17:E3:4C:E6:A2:50:A3:74:49:8D:99:84:F8:84:AA:
  • E3:8D:FD:C5:04:00:3E:0A