SSL-Tools

SSL check results of bllmnn.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for bllmnn.de 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 Thu, 28 Mar 2024 11:35:45 +0000

The mailservers of bllmnn.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @bllmnn.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.bllmnn.de
2a03:4000:1a:1d5::1
 10
supported
mail.bllmnn.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.bllmnn.de
185.162.248.209
 10
supported
mail.bllmnn.de
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 @bllmnn.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.bllmnn.de

Certificate chain
  • mail.bllmnn.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.bllmnn.de
Alternative Names
  • mail.bllmnn.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-08
Not valid after
2024-06-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
54:BB:78:F7:8B:DC:75:25:56:42:0D:E9:54:C8:A8:9E:86:A5:C5:29:4A:8C:EB:17:D0:E9:7B:56:5A:9F:D9:CD
SHA1
DD:2D:4D:C7:A4:2F:B0:7F:C6:FA:1F:63:37:73:17:96:D1:F9:FE:50
X509v3 extensions
subjectKeyIdentifier
  • A5:FA:81:9E:99:83:38:46:1B:47:10:99:65:2E:A0:4A:A6:7B:AE:BA
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 8 13:10:41.111 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C0:02:D8:F9:3D:64:AC:43:FC:82:CE:
  • 05:CD:91:6C:44:62:67:74:11:82:12:33:F4:A7:E8:57:
  • 66:E3:69:0B:E7:02:21:00:B3:82:7F:5C:2E:7C:EB:6D:
  • 7D:3D:BD:05:18:84:43:CD:6B:48:61:21:AA:C9:19:72:
  • 16:C5:25:15:76:80:F5:BB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 8 13:10:41.099 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1B:6A:CC:D7:85:5B:B3:1E:04:D6:0D:B7:
  • A5:31:68:00:AF:7B:25:A2:FE:A7:75:5A:B6:09:67:93:
  • 37:64:C4:36:02:21:00:A1:59:7B:B0:FC:48:02:0C:98:
  • 79:00:ED:09:0B:8A:AE:DB:00:8C:D0:88:35:DC:56:4D:
  • 65:CB:32:14:40:70:39

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