SSL-Tools

SSL check results of b2tmaquinaseferramentas.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for b2tmaquinaseferramentas.com.br 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 Tue, 25 Mar 2025 21:31:02 +0000

The mailservers of b2tmaquinaseferramentas.com.br can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @b2tmaquinaseferramentas.com.br addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.b2tmaquinaseferramentas.com.br
192.185.217.39
 0
supported
b2tmaquinaseferramentas.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
42 s

Outgoing Mails

We have not received any emails from a @b2tmaquinaseferramentas.com.br address so far. Test mail delivery

Certificates

First seen at:

CN=b2tmaquinaseferramentas.com.br

Certificate chain
  • b2tmaquinaseferramentas.com.br
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • b2tmaquinaseferramentas.com.br
Alternative Names
  • *.b2tmaquinaseferramentas.com.br
  • b2tmaquinaseferramentas.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-02-13
Not valid after
2025-05-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D4:7E:86:8E:E9:55:87:C4:8F:43:79:44:E5:4A:75:AA:4F:F0:4D:F0:B4:F7:59:A6:3F:F0:0F:2B:AB:84:01:5E
SHA1
29:C4:8B:10:AC:1B:CD:51:8E:9A:5E:BA:1C:94:C0:E0:6E:6D:4B:D1
X509v3 extensions
subjectKeyIdentifier
  • BC:8B:66:F6:00:7A:D5:0D:C3:76:22:68:35:D5:D1:59:BA:56:34:5F
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Feb 13 06:19:37.424 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:32:F2:56:26:DF:21:7D:63:58:3C:D0:4E:
  • 27:12:F2:79:CD:2D:A5:C9:1A:FD:2E:67:39:0D:3F:A8:
  • FF:45:1C:B1:02:21:00:A7:7C:1F:C7:8F:9A:1C:B7:46:
  • 38:73:A9:9D:50:AB:0C:72:FE:EA:2F:3A:FE:9A:22:C3:
  • D8:FA:6A:39:66:45:5D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Feb 13 06:19:37.770 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1B:AD:B1:01:C5:F2:39:04:0C:AE:DD:6F:
  • E5:A9:DB:1D:F9:CE:43:46:9D:35:B7:77:80:64:14:C3:
  • FC:99:6C:7B:02:21:00:AF:3E:FB:71:2C:A7:55:C3:E5:
  • 22:8B:54:39:D8:D2:C1:A6:B2:7A:83:65:93:23:6C:B5:
  • AB:BB:4C:82:9B:A1:17