SSL check results of ra-hintermayr.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for ra-hintermayr.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, 22 Jan 2025 14:19:19 +0000

We can not guarantee a secure connection to the mailservers of ra-hintermayr.de!

Please contact the operator of ra-hintermayr.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/ra-hintermayr.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @ra-hintermayr.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.ra-hintermayr.de
185.243.11.135
10
supported
ra-hintermayr.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
rw0b87.webhosting.systems
185.243.11.135
Results incomplete
50
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=ra-hintermayr.de

Certificate chain
  • ra-hintermayr.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • ra-hintermayr.de
Alternative Names
  • ra-hintermayr.de
  • webmail.ra-hintermayr.de
  • www.ra-hintermayr.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-17
Not valid after
2025-04-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B4:FF:70:2F:79:01:20:3B:CA:29:A8:BB:65:89:57:F3:F6:17:F9:A3:0F:08:D0:B1:4C:74:84:C7:BA:EF:B5:0C
SHA1
A0:43:3A:1A:10:3D:7B:E1:46:A4:0D:3D:26:3C:08:39:F8:01:4A:98
X509v3 extensions
subjectKeyIdentifier
  • D1:26:F1:2E:35:00:A0:67:18:D6:6B:42:4D:41:A0:97:F5:55:04:12
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
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 : Jan 17 07:47:30.803 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0B:7B:6A:6E:5C:0E:C3:B4:7C:B2:C2:57:
  • 4D:9B:EB:E6:E6:31:ED:50:D9:AE:CB:97:89:1F:83:E9:
  • 9E:7A:35:BE:02:21:00:CD:1A:20:E4:0B:8C:76:5A:28:
  • 7F:CB:6E:11:26:56:FA:EB:99:99:1A:7C:61:3D:57:2E:
  • F4:BF:15:DB:F5:92:18
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 17 07:47:32.771 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:51:71:76:5B:15:9E:49:24:AD:EA:6C:5A:
  • 4A:24:D5:4F:73:A3:ED:8B:D0:3E:4B:48:A6:7B:3C:24:
  • 4F:6B:CA:29:02:20:6E:55:5B:E7:C0:75:4D:4A:82:5F:
  • 98:B9:16:70:AB:BE:F3:04:40:86:FB:8A:76:5F:D6:22:
  • 71:F9:CD:AA:78:4B