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

Report created Wed, 07 Apr 2021 01:00:01 +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
116.203.12.91
10
supported
*.temesinko.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
mx2.temesinko.net
116.203.12.92
Results incomplete
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,OU=Domain Control Validated

Certificate chain
Subject
Organizational Unit (OU)
  • Domain Control Validated
Common Name (CN)
  • *.temesinko.net
Alternative Names
  • *.temesinko.net
  • temesinko.net
Issuer
Country (C)
  • BE
Organization (O)
  • GlobalSign nv-sa
Common Name (CN)
  • AlphaSSL CA - SHA256 - G2
validity period
Not valid before
2019-06-22
Not valid after
2021-06-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3D:80:1E:9F:2C:74:BA:5D:9C:66:B2:23:FD:4B:3B:C8:38:8E:05:C9:67:A4:88:72:34:30:6F:52:5A:34:6C:20
SHA1
4D:15:E1:1D:ED:BF:91:22:31:CA:A0:C8:DD:72:5E:1C:BF:F4:3B:E6
X509v3 extensions
authorityInfoAccess
  • CA Issuers - URI:http://secure2.alphassl.com/cacert/gsalphasha2g2r1.crt
  • OCSP - URI:http://ocsp2.globalsign.com/gsalphasha2g2
certificatePolicies
  • Policy: 1.3.6.1.4.1.4146.1.10.10
  • CPS: https://www.globalsign.com/repository/
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://crl2.alphassl.com/gs/gsalphasha2g2.crl
authorityKeyIdentifier
  • keyid:F5:CD:D5:3C:08:50:F9:6A:4F:3A:B7:97:DA:56:83:E6:69:D2:68:F7
subjectKeyIdentifier
  • C5:E3:63:B0:DE:4D:47:B1:D0:8A:5D:6F:71:F8:D8:93:E7:69:D6:19
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47:
  • 38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85
  • Timestamp : Jun 22 01:08:43.698 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B2:38:3F:85:E5:40:BA:62:65:33:9F:
  • C4:FE:89:09:A6:27:AF:4F:79:12:13:DC:1C:82:A7:41:
  • 8F:E5:85:08:6E:02:21:00:AB:B1:E6:D3:69:5D:84:21:
  • 90:F1:64:CF:6D:C3:EC:68:31:41:CB:C6:50:FA:63:76:
  • 91:94:EE:C1:02:1F:44:85
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jun 22 01:08:43.806 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E0:EE:65:F7:E2:AD:C4:CE:A2:53:64:
  • 05:28:DC:DF:F2:2F:6B:69:F4:EB:6F:99:35:45:1C:95:
  • F6:63:27:FD:3C:02:20:4F:96:55:B1:8B:22:6D:0D:00:
  • C8:C0:76:EE:CA:C4:E5:B3:74:37:42:2E:2B:BB:12:D6:
  • 68:92:EA:24:F2:63:51
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 55:81:D4:C2:16:90:36:01:4A:EA:0B:9B:57:3C:53:F0:
  • C0:E4:38:78:70:25:08:17:2F:A3:AA:1D:07:13:D3:0C
  • Timestamp : Jun 22 01:08:43.536 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:45:2A:0A:82:14:12:9B:AA:7C:5B:65:47:
  • 71:C0:C6:60:06:3C:4D:4B:B7:BC:34:E0:AE:A3:1E:D5:
  • 9A:69:FC:5F:02:21:00:E6:84:0D:26:2F:0A:E4:04:1E:
  • C3:2B:BB:FA:08:B7:F7:57:AF:88:39:22:0D:88:81:3C:
  • FF:39:39:B4:8E:7B:BF

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