SSL-Tools

SSL check results of temesinko.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for temesinko.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 Fri, 12 Jul 2024 12:25:39 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.temesinko.net
2a01:4f8:1c1c:5291::1
 10
supported
temesinko.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s
mx1.temesinko.net
116.203.12.91
 10
supported
temesinko.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mx2.temesinko.net
2a01:4f8:c0c:cad0::1
 20
supported
temesinko.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mx2.temesinko.net
116.203.198.145
 20
supported
temesinko.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

We have received emails from these servers with @temesinko.de sender addresses. Test mail delivery

Host TLS Version & Cipher
mx1.temesinko.net (116.203.12.91)
TLSv1.3 TLS_AES_256_GCM_SHA384
de1-gw-static.temesinko.net (87.128.48.5)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=temesinko.net

Certificate chain
  • temesinko.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • temesinko.net
Alternative Names
  • *.temesinko.net
  • temesinko.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-06-05
Not valid after
2024-09-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
76:4D:F5:64:AA:89:4E:6E:88:5A:43:5D:F9:CA:2C:C8:C8:50:FD:AB:3B:0A:96:2A:56:ED:DE:13:C1:CC:B9:78
SHA1
7F:30:51:D2:E3:5A:7A:F4:74:36:70:30:02:81:CE:4B:1D:01:4F:FF
X509v3 extensions
subjectKeyIdentifier
  • F9:9C:AA:1C:5D:7D:B9:B8:C3:A8:B4:DC:FB:F9:8E:34:49:D2:D6:5E
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Jun 5 22:19:13.100 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7C:9E:4C:C8:EB:C3:EA:04:AC:28:85:69:
  • 71:1D:F4:17:84:FD:12:A6:7D:C0:36:F7:6D:D2:D0:4B:
  • 1D:81:64:20:02:20:5D:99:7A:63:EF:94:A1:2D:B3:F5:
  • 27:F1:2C:2A:0C:D5:A8:C1:93:88:2F:11:C9:AA:AC:B7:
  • F7:25:7A:2D:37:8C
  • 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 : Jun 5 22:19:13.106 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0E:94:50:2F:37:E0:23:48:9F:DF:E5:05:
  • CA:CB:51:13:3B:D2:EA:0C:24:55:ED:D8:D9:5B:B1:1F:
  • E0:86:51:7D:02:21:00:FA:97:0C:A4:13:BE:20:C9:1E:
  • BE:BC:47:70:C6:C5:BC:03:6E:38:8F:56:B1:55:F7:70:
  • 59:DA:D9:88:BD:65:17

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.mx1.temesinko.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mx2.temesinko.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid