SSL-Tools

SSL check results of allurelog.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for allurelog.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 Fri, 24 May 2024 09:02:24 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

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

Certificates

First seen at:

CN=allurelog.com.br

Certificate chain
  • allurelog.com.br
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • allurelog.com.br
Alternative Names
  • *.allurelog.com.br
  • allurelog.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-06
Not valid after
2024-07-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A6:14:1B:D8:50:35:D3:90:5B:78:FE:C2:69:5E:74:0C:F5:6C:5F:28:44:C4:E4:3C:24:30:AA:03:AF:92:F1:E0
SHA1
59:C7:7A:86:AB:D5:67:E0:0A:89:A1:9D:57:56:D8:F6:8A:28:43:B1
X509v3 extensions
subjectKeyIdentifier
  • 4E:46:42:62:50:2A:90:DC:6B:14:CC:C1:77:2C:2B:1F:4B:C1:C9:8C
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 6 20:22:24.974 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EC:17:39:90:7F:1A:61:33:54:85:88:
  • 40:47:BD:10:09:1B:90:9D:0D:2B:FB:90:D1:71:D6:6A:
  • 56:7E:75:E2:3F:02:20:53:5E:1B:5D:4D:1C:77:4A:DA:
  • A1:72:9B:53:93:BF:26:00:69:1C:2B:C6:21:F5:89:72:
  • 83:53:FB:A8:5A:D4:FD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 6 20:22:24.980 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:48:E1:41:39:CA:94:71:9D:BC:0E:50:63:
  • D4:4A:B6:E6:E1:BE:DD:65:F1:D0:5C:72:9D:63:36:51:
  • 03:92:A9:83:02:20:62:4D:D9:35:B0:79:2D:8A:26:0E:
  • 7D:FA:72:EC:7D:B2:97:7A:D0:CA:F9:D7:B8:9F:E1:27:
  • F0:6E:DB:1B:3A:1D