SSL-Tools

SSL check results of glamory.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for glamory.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 Thu, 25 Apr 2024 10:05:16 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.glamory.de
87.118.84.155
 10
supported
mail.glamory.de
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 @glamory.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.glamory.de

Certificate chain
  • mail.glamory.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.glamory.de
Alternative Names
  • mail.glamory.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-25
Not valid after
2024-07-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
03:6D:CB:2B:1D:89:00:42:52:52:71:70:34:C0:AA:F7:99:7F:6D:0B:04:38:89:5D:FB:DA:98:15:4F:B8:31:AC
SHA1
D1:54:BB:EB:9F:1F:0C:62:78:C1:45:AD:CA:BD:34:EA:94:69:0A:41
X509v3 extensions
subjectKeyIdentifier
  • 86:9D:72:14:B6:A6:1A:93:00:32:7F:43:07:3C:16:15:BE:47:EF:3F
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 : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 25 09:58:12.282 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2A:15:3C:91:10:64:66:DB:B9:80:69:DA:
  • 5A:E5:3F:EB:B1:C1:ED:79:5E:68:AB:EA:C8:AB:80:5C:
  • 90:1D:4C:A5:02:21:00:96:C1:76:5F:8F:AF:4D:1B:80:
  • F5:6E:7E:42:36:8F:10:52:52:18:9B:C4:65:BC:7A:BC:
  • E5:18:71:06:B8:61:C1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 25 09:58:12.337 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:84:8B:F1:CD:DC:7A:34:D8:86:25:B3:
  • 67:51:FA:EE:87:EC:DD:2D:CB:2A:A4:B0:E1:F0:B9:ED:
  • 5D:88:F1:E9:B0:02:21:00:F6:ED:01:3A:A6:44:A3:E9:
  • 2C:12:85:0C:43:6C:15:B6:E0:44:65:47:92:2E:E9:A7:
  • BB:40:16:10:D0:F7:EC:F9