SSL-Tools

SSL check results of aplusg.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for aplusg.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 Wed, 23 Jul 2025 11:43:37 +0000

We can not guarantee a secure connection to the mailservers of aplusg.de!

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

/mailservers/aplusg.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx3.aplusg.de
80.242.164.97
 10
supported
mx3.aplusg.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
relay.sybcom.net
213.147.3.15
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx3.aplusg.de

Certificate chain
  • mx3.aplusg.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Expired
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx3.aplusg.de
Alternative Names
  • mx3.aplusg.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-07-15
Not valid after
2024-10-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F6:C2:39:50:FA:34:EF:EA:62:62:73:17:D7:C5:3C:8A:4D:F9:16:F8:62:70:2A:4C:2C:7C:E3:F8:D8:FA:49:F8
SHA1
15:16:65:96:E8:AA:B1:89:4E:E0:DE:D3:BF:48:63:FD:75:36:44:6A
X509v3 extensions
subjectKeyIdentifier
  • 44:27:75:06:DA:70:A8:E7:C1:82:23:51:D4:01:EA:99:42:97:AF:B5
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.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 : Jul 15 09:30:43.078 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AC:6C:47:71:36:5B:E8:EC:56:AF:39:
  • 86:02:7A:4A:31:3A:93:B5:BD:29:26:B2:2E:40:F1:DC:
  • CA:28:7A:A3:89:02:21:00:91:6D:68:1E:D1:8E:A2:64:
  • 8A:1F:89:BE:55:2E:91:F7:F0:E5:CE:F2:B9:4A:2C:C0:
  • BB:09:F7:35:AA:54:17:90
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Jul 15 09:30:43.272 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:06:8B:2E:57:71:AC:C1:9C:DF:02:AB:05:
  • 60:9C:43:32:9D:48:AD:94:C9:51:98:C5:7E:8C:B5:B2:
  • 23:BC:CD:CB:02:20:7A:AC:50:FF:CA:B7:6D:DB:1A:94:
  • 85:35:E5:62:05:D9:0C:DF:76:5D:F4:5D:C2:41:E4:04:
  • 04:42:9B:AE:3C:A6