SSL-Tools

SSL check results of drac-vercors-escalade.fr

NEW You can also bulk check multiple servers.

Discover if the mail servers for drac-vercors-escalade.fr 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, 22 Jan 2025 19:54:54 +0000

The mailservers of drac-vercors-escalade.fr can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @drac-vercors-escalade.fr addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.girofle.org
2001:41d0:1004:f61::
 10
supported
mail.girofle.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
mail.girofle.org
149.202.95.97
 10
supported
mail.girofle.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @drac-vercors-escalade.fr address so far. Test mail delivery

Certificates

First seen at:

CN=mail.girofle.org

Certificate chain
  • mail.girofle.org
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.girofle.org
Alternative Names
  • mail.girofle.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-04
Not valid after
2025-04-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9F:F2:2D:45:E9:09:E4:74:6B:92:D4:0D:3C:4A:0E:E7:2B:67:02:F4:15:FA:20:9A:FE:EF:DC:76:15:4A:E9:56
SHA1
70:6C:DF:7A:40:69:DC:3A:08:BE:89:58:91:5E:C0:4C:79:EC:1C:46
X509v3 extensions
subjectKeyIdentifier
  • 1B:5C:60:2A:72:2F:1F:18:12:78:67:0E:61:45:B3:30:2F:79:83:21
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 : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 4 19:49:05.797 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C0:38:7A:03:01:00:58:93:B1:56:98:
  • AA:2F:D5:B1:32:F3:23:47:5B:26:45:20:20:44:38:08:
  • 95:A5:0F:CC:42:02:21:00:FE:6A:D9:06:27:E9:DF:F5:
  • E3:AB:97:67:C7:83:FA:08:0D:85:92:72:07:45:48:9C:
  • EB:44:49:D3:84:9B:FA:18
  • 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 : Jan 4 19:49:06.015 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8F:74:66:6E:E4:9E:15:1F:39:5B:4F:
  • 77:C9:3B:00:A6:F0:CD:D7:E1:08:23:25:15:89:2B:13:
  • 37:F6:AD:D4:9C:02:20:31:3C:B6:3C:5F:16:2E:7D:32:
  • D4:E3:D2:19:7D:56:A1:91:3F:34:0B:4D:EF:40:DF:E8:
  • 6F:26:44:83:00:0D:D8

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.mail.girofle.org
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
error
Debug
valid