SSL-Tools

SSL check results of ruhrstadt-medien.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for ruhrstadt-medien.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 Tue, 23 Apr 2024 14:29:57 +0000

The mailservers of ruhrstadt-medien.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @ruhrstadt-medien.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail02.mail-gw.de
95.130.17.235
 10
supported
*.mail-gw.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
12 s
mail03.mail-gw.de
95.130.17.227
 20
supported
*.mail-gw.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
12 s

Outgoing Mails

We have not received any emails from a @ruhrstadt-medien.de address so far. Test mail delivery

Certificates

First seen at:

CN=*.mail-gw.de

Certificate chain
Subject
Common Name (CN)
  • *.mail-gw.de
Alternative Names
  • *.mail-gw.de
  • mail-gw.de
Issuer
Country (C)
  • GB
State (ST)
  • Greater Manchester
Locality (L)
  • Salford
Organization (O)
  • Sectigo Limited
Common Name (CN)
  • Sectigo RSA Domain Validation Secure Server CA
validity period
Not valid before
2024-03-15
Not valid after
2025-04-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AF:FA:59:FB:F2:EA:C7:BB:5A:96:9A:82:0A:DE:84:81:70:46:C9:19:03:0F:44:0F:3F:B8:E7:69:61:6F:35:CE
SHA1
A4:D2:49:D0:57:34:5F:E7:86:84:FD:76:9E:62:8B:C5:78:4F:D9:1A
X509v3 extensions
authorityKeyIdentifier
  • keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
subjectKeyIdentifier
  • 32:D3:50:1E:6F:42:2A:89:30:72:8D:6B:3F:44:53:91:54:2D:D2:18
certificatePolicies
  • Policy: 1.3.6.1.4.1.6449.1.2.2.7
  • CPS: https://sectigo.com/CPS
  • Policy: 2.23.140.1.2.1
authorityInfoAccess
  • CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
  • OCSP - URI:http://ocsp.sectigo.com
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Mar 15 13:24:58.879 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F5:31:92:90:E8:08:AF:4B:73:C0:EE:
  • 26:50:88:B0:22:74:6B:54:E8:F5:02:53:AE:8C:38:E5:
  • A0:D8:B2:54:7B:02:21:00:EA:0D:1E:78:3E:B7:E7:CE:
  • 54:88:75:DF:68:2D:D4:98:8E:7D:98:01:6D:36:A4:E6:
  • 75:4A:BD:3E:C5:53:78:91
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Mar 15 13:24:58.786 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FF:09:34:FE:A3:42:5A:88:41:68:10:
  • B9:C3:10:86:88:92:03:39:72:3E:09:F5:40:C3:0B:CC:
  • 60:E3:25:22:DA:02:20:0A:53:6B:8F:1B:11:F6:71:5E:
  • 0F:0A:BD:3D:EB:CB:4B:60:33:AA:91:5B:25:0E:81:DF:
  • 90:6C:6A:06:DC:09:87
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Mar 15 13:24:58.814 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CF:19:98:B5:A7:1E:5B:1A:65:1D:4E:
  • 01:62:82:9A:D2:27:6A:87:23:E4:02:68:10:9B:A3:1C:
  • F3:18:33:4D:CB:02:20:44:EC:72:35:EF:22:77:EA:AB:
  • A6:94:37:99:24:39:FC:89:0C:94:85:88:42:03:0E:D5:
  • 35:68:B9:65:C3:5E:37