SSL check results of behringer.me

NEW You can also bulk check multiple servers.

Discover if the mail servers for behringer.me 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

Report created Thu, 25 Apr 2024 13:42:00 +0000

The mailservers of behringer.me can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @behringer.me addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.behringer.me
2a02:c207:2066:8664::1
10
supported
mail.behringer.me
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail.behringer.me
161.97.80.95
10
supported
mail.behringer.me
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

We have received emails from these servers with @behringer.me sender addresses. Test mail delivery

Host TLS Version & Cipher
forward104o.mail.yandex.net (37.140.190.179)
TLSv1.2 AECDH-AES256-SHA

Certificates

First seen at:

CN=mail.behringer.me

Certificate chain
  • mail.behringer.me
    • 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.behringer.me
Alternative Names
  • autoconfig.behringer.me
  • autodiscover.behringer.me
  • mail.behringer.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-22
Not valid after
2024-06-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
0B:D8:BC:10:C9:DF:16:EF:19:5C:9C:88:A4:C2:23:E2:45:97:FC:2D:7E:8E:30:79:A1:31:51:73:C8:E7:91:C7
SHA1
7A:B4:15:6F:7E:5E:72:DE:72:D2:F5:59:0E:8A:15:DC:D9:CA:4C:E7
X509v3 extensions
subjectKeyIdentifier
  • DF:89:79:FE:D5:7E:85:A1:94:5A:CC:88:F5:B8:4C:3C:99:60:93:0F
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 22 12:20:48.466 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:30:B4:CA:5C:22:69:AB:C5:FA:30:94:AF:
  • 5D:32:8A:08:55:F7:BA:0C:7C:BE:CC:98:C1:58:1D:4C:
  • CF:F3:66:ED:02:21:00:D0:EB:1F:C6:E7:24:9A:5B:85:
  • 88:EC:8B:A6:16:B8:06:C4:C0:C6:17:1B:C1:57:5A:01:
  • 9F:AB:58:67:F2:73:AA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 22 12:20:48.486 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:19:0E:7C:AA:CF:E2:17:F9:98:69:45:68:
  • 6A:63:14:F7:5B:9A:2D:68:5E:98:35:05:72:E3:4B:F2:
  • 03:AC:49:6F:02:20:34:8D:1B:5D:45:A3:1F:A7:36:60:
  • FE:9E:C0:FB:58:68:64:D1:C4:06:5E:E9:FD:99:5E:22:
  • 1F:D7:E4:AA:29:91

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