SSL check results of xendynastie.at

NEW You can also bulk check multiple servers.

Discover if the mail servers for xendynastie.at 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 Tue, 24 Sep 2024 17:41:52 +0000

The mailservers of xendynastie.at can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @xendynastie.at addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
yu.xendynastie.at
2a02:c206:2210:9659::1
Results incomplete
10 not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
yu.xendynastie.at
109.199.107.129
10
supported
xendynastie.at
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

We have not received any emails from a @xendynastie.at address so far. Test mail delivery

Certificates

First seen at:

CN=xendynastie.at

Certificate chain
  • xendynastie.at
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • xendynastie.at
Alternative Names
  • auth.xendynastie.at
  • backup.xendynastie.at
  • cloud.xendynastie.at
  • git.xendynastie.at
  • monitor.xendynastie.at
  • photos.xendynastie.at
  • xendynastie.at
  • yu.xendynastie.at
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-09-14
Not valid after
2024-12-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BC:C9:99:71:40:56:CB:62:4B:64:BB:8A:9B:8A:F8:B6:52:AD:DA:F3:44:89:C0:93:66:C6:A5:88:E9:EE:F4:FA
SHA1
B7:56:E9:5B:DA:CB:93:FB:06:0F:E7:12:3F:CC:66:47:53:42:5E:18
X509v3 extensions
subjectKeyIdentifier
  • 57:AC:75:B1:25:9B:16:66:FB:9C:35:B2:95:90:B7:DB:17:9D:C8:5C
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 14 22:56:01.615 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:47:20:31:97:96:EB:C7:54:4F:4A:EF:B5:
  • 93:EC:E7:1B:78:AB:E9:BF:83:40:0F:A6:47:C2:EC:54:
  • 2F:CB:83:5E:02:21:00:FB:6B:5B:E8:27:EE:6B:67:0B:
  • 71:C4:4B:4E:A8:DE:B2:6D:FE:A9:60:EB:02:3D:7C:06:
  • 96:1C:94:EC:58:FF:4A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Sep 14 22:56:03.950 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1E:A9:E5:82:CB:63:1A:2A:B8:72:BD:4A:
  • 16:1F:83:B9:F7:F0:52:07:27:7B:37:C6:4A:E6:7B:3C:
  • 1C:CD:8B:CA:02:21:00:A2:59:AA:84:0A:46:EF:65:33:
  • BF:EB:AD:44:0F:0B:8E:53:54:BC:53:97:F3:10:B6:78:
  • F9:0F:4C:FB:66:80:33

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