SSL-Tools

SSL check results of beutlich.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for beutlich.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 Sat, 10 May 2025 00:31:37 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.beutlich.org
2a01:4f8:c013:302d::1
 11
supported
mail.beutlich.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.beutlich.org
78.47.135.135
 11
supported
mail.beutlich.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.beutlich.org

Certificate chain
  • mail.beutlich.org
    • 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.beutlich.org
Alternative Names
  • autoconfig.beutlich.org
  • autodiscover.beutlich.org
  • mail.beutlich.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-03-30
Not valid after
2025-06-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1F:F4:84:55:EE:48:E0:BB:DE:7F:84:CC:FA:DF:82:AC:57:29:A3:7C:15:81:49:9E:93:28:B5:54:12:77:3E:54
SHA1
16:4E:F3:A5:0F:C5:DA:27:BA:EC:BD:E7:0B:62:01:0C:71:32:A1:1E
X509v3 extensions
subjectKeyIdentifier
  • F0:72:6B:5E:E8:92:DC:B1:04:D5:2D:47:CC:08:71:5F:4B:0A:C0:3D
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
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/6.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Mar 30 14:05:00.621 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C4:DB:41:5B:98:C9:AC:AE:89:5E:D5:
  • 9C:8F:42:33:70:2A:C3:77:E9:1A:F2:44:0E:B8:E0:23:
  • 4A:DD:FB:C5:15:02:21:00:AB:0C:72:E1:92:AE:C2:DE:
  • 88:C0:4F:72:71:80:39:6C:6B:2E:E1:08:8A:59:C0:5A:
  • 1F:72:E9:DE:B1:ED:D3:73
  • 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 : Mar 30 14:05:00.641 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9A:AC:3D:3E:C7:B4:FC:92:20:69:2D:
  • 30:7E:6E:CF:3B:B9:A7:44:0B:CB:2F:7C:E4:87:88:7E:
  • 7D:89:0A:AA:05:02:21:00:9C:37:65:4A:5D:80:3C:75:
  • 6F:F6:30:6F:62:90:7D:FD:AB:E9:55:D4:3D:85:23:E6:
  • DB:B1:4D:DC:24:A7:C8:DF