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 Tue, 18 Nov 2025 15:22:52 +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
8 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
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
      • R13
        • 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)
  • R13
validity period
Not valid before
2025-11-07
Not valid after
2026-02-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1B:B5:A6:C1:2C:F5:22:20:29:37:65:8A:BF:F9:ED:E2:1C:44:AA:2E:27:BE:E4:67:C9:5C:BA:76:C9:0A:78:55
SHA1
98:E0:68:6E:EC:A2:7E:FA:D4:74:1E:C2:B1:44:88:60:6D:71:98:39
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:E7:AB:9F:0F:2C:33:A0:53:D3:5E:4F:78:C8:B2:84:0E:3B:D6:92:33
authorityInfoAccess
  • CA Issuers - URI:http://r13.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r13.c.lencr.org/96.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:86:D4:C7:28:AA:6F:FE:BA:03:6F:78:2A:4D:01:91:
  • AA:CE:2D:72:31:0F:AE:CE:5D:70:41:2D:25:4C:C7:D4
  • Timestamp : Nov 7 15:40:51.659 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DD:76:11:8F:2E:01:8A:7B:F5:4F:98:
  • 48:7F:41:CC:44:06:49:DE:25:DA:90:A7:6A:D3:C1:91:
  • 87:3D:98:47:7D:02:20:05:CB:FE:0B:1F:06:E1:51:74:
  • B2:77:D6:DF:23:6B:4C:56:21:66:06:6B:43:2F:DA:63:
  • 8A:76:62:34:4B:2E:D6
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 96:97:64:BF:55:58:97:AD:F7:43:87:68:37:08:42:77:
  • E9:F0:3A:D5:F6:A4:F3:36:6E:46:A4:3F:0F:CA:A9:C6
  • Timestamp : Nov 7 15:40:51.736 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:34:1D:30:DA:5C:B6:3D:77:88:0B:5D:E3:
  • D6:0A:87:99:78:A3:64:63:77:68:DF:6F:74:C1:56:C7:
  • A1:EC:BB:B7:02:20:43:D9:93:C1:22:62:85:43:F8:BC:
  • 59:64:86:D5:62:21:FB:39:86:9F:DB:4E:97:2C:15:EC:
  • E6:2E:64:A2:3D:A2

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