SSL-Tools

SSL check results of danborg.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for danborg.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 Wed, 15 Sep 2021 18:29:45 +0000

We can not guarantee a secure connection to the mailservers of danborg.org!

Please contact the operator of danborg.org and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/danborg.org

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.danborg.org
80.197.112.117
 10
supported
danborg.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
smtp.kestler.dk
87.59.104.61
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=danborg.org

Certificate chain
  • danborg.org
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • danborg.org
Alternative Names
  • danborg.org
  • www.danborg.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-09-15
Not valid after
2021-12-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
79:18:A2:DC:34:7C:1F:F5:81:76:24:83:82:D3:0A:69:63:DF:61:4B:0C:A9:32:CB:7D:1C:73:9A:22:CD:41:C3
SHA1
64:80:2B:9B:DA:47:9A:16:82:BB:8B:4C:33:51:BA:B2:11:CA:0D:11
X509v3 extensions
subjectKeyIdentifier
  • E1:18:B4:D8:88:C4:F9:E9:BB:35:93:5C:68:59:D6:6E:90:23:AD:15
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 : Sep 15 18:13:28.617 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:69:5F:3F:3E:AC:E8:66:C1:12:3E:A9:56:
  • F2:5C:F1:14:34:94:6C:5D:C1:DE:76:D2:9F:12:25:E9:
  • 09:31:4E:7A:02:20:35:8A:D2:18:BD:98:8F:F3:5A:FE:
  • A2:E6:26:54:A9:09:F1:AA:B4:A8:9E:0F:A9:C0:42:D9:
  • 12:7F:F8:31:07:C7
  • 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 : Sep 15 18:13:28.595 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:55:DE:C7:00:C9:AC:9B:75:AF:93:09:A0:
  • 3B:55:40:E9:66:CC:25:6E:45:C8:60:72:6A:B9:60:45:
  • D2:5E:40:74:02:20:7D:2D:57:7A:71:67:0B:20:84:51:
  • 00:BA:5A:3E:7E:9C:D8:D9:CA:8B:BB:5E:83:BF:D1:E7:
  • 5B:B6:81:6E:FA:99