SSL check results of muessig.family

NEW You can also bulk check multiple servers.

Discover if the mail servers for muessig.family 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, 08 Apr 2021 07:29:14 +0000

The mailservers of muessig.family can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @muessig.family addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
kamino.tech-ninja.de
2a01:4f8:140:50de::2
20
supported
tech-ninja.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
kamino.tech-ninja.de
88.198.69.156
20
supported
tech-ninja.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

We have received emails from these servers with @muessig.family sender addresses. Test mail delivery

Host TLS Version & Cipher
kamino.tech-ninja.de (88.198.69.156)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=tech-ninja.de

Certificate chain
  • tech-ninja.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • tech-ninja.de
Alternative Names
  • *.tech-ninja.de
  • tech-ninja.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-08
Not valid after
2021-05-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E9:B7:CC:0E:6D:CC:13:EB:F4:6D:B8:59:44:88:1A:6D:71:52:16:2B:B3:34:CB:DD:5F:21:F0:AD:3A:BB:9F:A4
SHA1
EA:D9:A5:14:81:03:46:75:A2:F0:0E:56:7F:90:F5:DD:9C:AB:83:49
X509v3 extensions
subjectKeyIdentifier
  • 47:37:74:1D:74:C1:A8:D7:75:DA:5F:AD:BD:7B:14:86:17:76:7B:AE
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Feb 8 23:30:54.564 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9A:65:B7:81:91:F0:6E:35:2A:34:35:
  • 7F:E5:C6:6A:4B:91:E8:F4:3F:01:73:1D:C6:FB:CE:8A:
  • 35:E6:DF:E3:2C:02:20:0B:B0:1A:6B:AA:B4:73:F6:2C:
  • 8C:D4:A7:B0:68:85:BE:AE:50:B8:A5:30:42:0C:DE:5D:
  • 54:4F:59:9B:42:F7:8F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Feb 8 23:30:54.594 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B1:D5:8B:A8:74:26:D5:9A:61:01:C6:
  • 65:70:9C:71:92:E7:81:AC:FD:09:74:FD:96:60:A3:5F:
  • 3E:25:91:9A:F3:02:21:00:95:F5:59:6F:E3:42:AB:D2:
  • BD:7A:FD:88:91:A1:59:1F:1B:6D:5E:0C:4B:58:45:34:
  • 06:E0:2F:97:09:A0:86:8C

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