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 Fri, 23 May 2025 08:21:42 +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
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
mail.beutlich.org
78.47.135.135
 11
supported
mail.beutlich.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 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
      • R11
        • 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
  • mta-sts.beutlich.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-05-11
Not valid after
2025-08-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
53:A3:96:52:6F:84:43:F2:D4:5C:97:AC:98:E5:18:05:44:CB:B4:62:34:53:BD:4E:6A:26:C6:D6:AF:F9:BC:25
SHA1
2D:54:98:9E:9B:63:F6:B9:FD:BF:E9:59:07:29:06:42:9B:FA:B1:FD
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:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/70.crl
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 : May 11 08:39:41.586 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:63:2E:89:E3:2C:D2:98:06:10:D9:91:13:
  • 20:54:F7:D1:42:C2:3D:B8:15:54:44:AD:D2:19:64:BA:
  • D0:1F:F2:02:02:21:00:B1:E4:2B:69:25:C1:51:21:4A:
  • 21:64:25:2B:7F:37:1D:61:E1:43:B3:2C:73:F7:FB:E4:
  • DD:09:6D:76:4B:19:86
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : May 11 08:39:41.561 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:97:B3:4D:EC:70:14:69:F8:93:A6:D0:
  • 32:CA:7B:76:08:45:C4:7F:58:F0:47:8D:E8:23:DE:73:
  • B4:72:38:B8:E8:02:21:00:B0:DA:BB:47:6B:68:3D:1F:
  • 15:28:44:01:48:43:BD:A1:75:99:B4:74:F0:42:22:A5:
  • 8E:1A:10:3C:28:6D:1F:5A

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.mail.beutlich.org
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid