SSL check results of blazic.rs

NEW You can also bulk check multiple servers.

Discover if the mail servers for blazic.rs 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 Sun, 26 Jan 2025 01:31:19 +0000

The mailservers of blazic.rs can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @blazic.rs addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.blazic.rs
2602:fbf9::10
10
supported
mail.blazic.rs
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
mail.blazic.rs
207.90.251.10
10
supported
mail.blazic.rs
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.blazic.rs

Certificate chain
  • mail.blazic.rs
    • remaining
    • 384 bit
    • ecdsa-with-SHA384

      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.blazic.rs
Alternative Names
  • mail.blazic.rs
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-01-22
Not valid after
2025-04-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4E:3B:CF:2B:17:4C:99:16:31:15:23:B7:E2:5E:7E:B1:65:30:7F:9A:5E:42:70:8E:A9:C1:82:98:37:BC:9F:1B
SHA1
84:3A:AF:8A:CF:0B:B8:CF:51:3E:91:DC:EB:EC:42:DE:D3:FC:BC:C7
X509v3 extensions
subjectKeyIdentifier
  • E8:09:B8:D5:09:93:50:49:82:84:9F:D1:6F:3A:EC:8B:84:03:98:E1
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Jan 22 19:13:14.684 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DC:17:EB:65:9A:BB:B6:4A:8E:FC:95:
  • DA:5A:45:FA:12:CD:49:8A:3F:19:BC:8D:3F:7A:4D:C9:
  • 59:C3:6E:8A:9D:02:20:64:BC:CA:AB:05:5C:40:8A:8B:
  • 18:52:BC:14:DA:3F:17:6A:48:97:65:49:F6:81:C1:04:
  • 29:B9:03:AC:E6:39:7E
  • 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 : Jan 22 19:13:14.679 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3C:99:E4:33:FD:4D:4B:19:A9:55:4A:53:
  • 4B:A8:F7:94:60:63:CA:85:98:82:E7:F9:B4:86:4C:22:
  • 36:DC:C6:98:02:21:00:ED:81:87:88:81:0A:7A:0C:44:
  • BA:83:86:89:3D:73:50:1C:61:B0:B8:C6:A3:00:0B:7B:
  • 4C:42:D3:00:E6:E0:80