SSL-Tools

SSL check results of mail.klamer.bg

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.klamer.bg 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, 18 Apr 2024 13:45:07 +0000

The mailservers of mail.klamer.bg can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.klamer.bg addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.klamer.bg
77.71.0.36
 -
supported
klamer.bg
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=klamer.bg

Certificate chain
  • klamer.bg
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • klamer.bg
Alternative Names
  • finance.klamer.bg
  • klamer.bg
  • mail.klamer.bg
  • news.klamer.bg
  • pop3.klamer.bg
  • www.klamer.bg
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-13
Not valid after
2024-07-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
30:A2:B3:C2:AE:13:BA:1A:9B:E0:42:CA:81:E7:0B:96:D4:94:FA:1C:D5:56:B7:B7:3C:74:2E:BF:0D:A4:E0:87
SHA1
7A:CD:A6:6F:50:B8:39:28:4D:21:EF:3B:C9:72:F1:91:55:D8:C0:57
X509v3 extensions
subjectKeyIdentifier
  • 03:5F:56:9F:02:46:05:50:67:54:0D:30:F7:68:48:25:65:5C:05:4C
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 : 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 : Apr 13 04:11:02.596 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DE:45:22:81:5C:2A:DF:A3:12:D4:9E:
  • 30:24:6B:3C:A6:54:99:F2:F8:6F:EE:DF:C5:E6:84:6D:
  • 45:FF:71:3E:34:02:20:2B:4D:27:7B:66:1E:D7:3D:C0:
  • DC:B5:FA:C8:26:76:96:00:37:32:59:C5:97:76:59:68:
  • 9B:AA:BA:1E:EB:6D:DB
  • 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 13 04:11:02.635 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2D:AF:84:15:C8:81:A6:0B:60:AB:87:19:
  • 8E:69:EA:EE:F0:E0:2F:56:B5:48:96:3C:82:36:81:F2:
  • 0A:2B:9B:9B:02:20:59:70:63:7B:58:4F:3E:C7:36:47:
  • C9:98:18:D2:7A:94:8D:3E:A2:77:D8:F0:10:EA:64:51:
  • 94:22:5D:8C:51:B2