SSL-Tools

SSL check results of tikra.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for tikra.eu 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, 16 Apr 2024 20:00:34 +0000

The mailservers of tikra.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @tikra.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tikra.eu
2a03:4000:41:299:a836:1fff:fe84:7b04
 10
supported
mail.tikra.eu
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
mail.tikra.eu
85.209.48.12
 10
supported
mail.tikra.eu
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.tikra.eu

Certificate chain
  • mail.tikra.eu
    • 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.tikra.eu
Alternative Names
  • mail.tikra.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-11
Not valid after
2024-06-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C3:7C:3B:A0:9C:20:39:AC:07:54:8C:F6:A0:E1:0D:00:75:97:37:B5:15:D7:4A:B4:21:51:C7:1E:2C:09:28:80
SHA1
2E:26:BC:52:97:41:F3:AE:B6:D0:1D:64:80:5A:CA:74:E6:9F:FB:6D
X509v3 extensions
subjectKeyIdentifier
  • B5:B3:BF:E8:AB:2F:84:96:E4:1E:2B:65:AD:37:C9:91:FB:B6:ED:A9
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 11 14:30:46.576 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CE:CE:A3:1F:18:BA:13:4B:E6:72:5C:
  • FA:AB:49:46:57:5E:8D:4E:D7:8D:AE:AE:D5:5C:D4:9B:
  • BA:31:52:77:5A:02:20:4C:13:D0:15:9E:E4:B2:DB:6E:
  • 44:AA:0B:2C:41:67:F1:90:D7:36:11:35:51:9F:D8:57:
  • 02:D0:4F:17:17:46:B8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Mar 11 14:30:46.638 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:43:02:1F:24:4E:CE:A7:F2:7C:9E:A3:C1:77:9B:DB:
  • 1C:5C:C3:3E:6C:D4:C2:E5:69:46:CE:28:99:0C:2F:64:
  • D8:F3:9B:02:20:79:2E:8D:BF:E6:82:0B:59:54:B5:C9:
  • 58:12:01:0E:6D:1B:9D:C6:2D:06:F4:D2:CD:B5:01:34:
  • C0:2F:F8:06: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.tikra.eu
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid