SSL-Tools

SSL check results of baselogic.dev

NEW You can also bulk check multiple servers.

Discover if the mail servers for baselogic.dev 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, 24 Apr 2024 15:09:55 +0000

The mailservers of baselogic.dev can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @baselogic.dev addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.baselogic.dev
2a02:c206:3013:2334::1
 10
supported
mx.baselogic.dev
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mx.baselogic.dev
158.220.97.1
 10
supported
mx.baselogic.dev
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx.baselogic.dev

Certificate chain
  • mx.baselogic.dev
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx.baselogic.dev
Alternative Names
  • mx.baselogic.dev
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-08
Not valid after
2024-07-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
88:CB:70:47:70:36:94:EB:DF:09:BE:D2:A1:CA:BC:CF:C9:D9:43:A5:D3:E2:FC:E6:41:57:5A:95:A3:62:6A:A8
SHA1
C3:EB:D2:EB:D5:8D:BA:9A:B9:75:48:BE:77:6B:71:9A:DD:40:BB:B7
X509v3 extensions
subjectKeyIdentifier
  • 84:3F:4D:3D:96:64:2F:44:89:2C:C0:22:75:8F:84:E1:A9:D6:75:95
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Apr 8 07:25:17.173 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:02:28:6A:CB:B8:30:13:49:4F:04:23:BF:
  • 7F:DA:0C:3E:67:CB:A6:DE:C4:0D:68:31:23:A3:AF:97:
  • 11:23:2F:D1:02:20:59:DD:96:09:F6:31:FD:82:02:A4:
  • A0:9B:26:6F:58:EC:D6:06:C4:2A:C7:6C:C1:80:45:7D:
  • E6:AF:56:BA:41:DD
  • 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 8 07:25:17.243 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:56:52:B9:69:A5:44:59:30:18:9A:8B:77:
  • 7A:66:AF:A2:5F:DF:A9:62:23:82:62:87:98:CA:68:E8:
  • E8:16:C5:BA:02:21:00:F0:F7:20:1E:52:9D:79:DD:87:
  • BA:77:8F:61:29:3C:79:53:6F:2C:29:28:0B:52:3C:53:
  • 1B:95:8F:59:64:11:07

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mx.baselogic.dev
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid