SSL check results of laflanelle.fr

NEW You can also bulk check multiple servers.

Discover if the mail servers for laflanelle.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

Report created Fri, 23 May 2025 07:36:36 +0000

We can not guarantee a secure connection to the mailservers of laflanelle.fr!

Please contact the operator of laflanelle.fr and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/laflanelle.fr

Servers

Incoming Mails

These servers are responsible for incoming mails to @laflanelle.fr addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
lynx.piyou.com
2001:41d0:303:75e3::
10
supported
lynx.piyou.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
lynx.piyou.com
51.68.33.227
10
supported
lynx.piyou.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
puma.piyou.com
2001:41d0:8:6d43::1
Results incomplete
20
supported
not checked
DANE
errors
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
1 s
puma.piyou.com
37.59.50.67
Results incomplete
20
supported
not checked
DANE
errors
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=lynx.piyou.com

Certificate chain
  • lynx.piyou.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • lynx.piyou.com
Alternative Names
  • lynx.piyou.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-04-07
Not valid after
2025-07-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7F:2B:97:E6:BE:68:40:DD:6E:CE:47:A7:43:7F:85:1E:C4:B1:BD:73:C4:C2:84:76:C0:D9:8D:B5:59:D5:B4:2D
SHA1
7A:08:FA:E1:0E:9C:D7:FF:09:E9:FB:59:53:1D:98:98:F3:66:91:B9
X509v3 extensions
subjectKeyIdentifier
  • 54:0C:A6:CC:72:D7:3D:E3:94:9D:B6:66:9D:FA:A9:EC:D9:48:61:5B
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
crlDistributionPoints
  • Full Name:
  • URI:http://e5.c.lencr.org/47.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Apr 7 16:39:45.908 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:DC:25:D7:75:8A:1B:76:08:F6:F5:02:
  • 50:F5:BA:DF:42:FA:62:0E:5F:93:97:83:53:85:10:8A:
  • BD:20:40:DB:16:02:21:00:FB:BC:EE:99:67:C1:BB:58:
  • 7A:6D:D8:45:70:8F:A1:89:A7:08:69:2C:3A:63:53:12:
  • 40:A0:94:5B:5A:14:46:C8
  • 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 : Apr 7 16:39:47.909 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AC:24:55:D0:CC:17:1D:63:4B:58:FA:
  • 9E:94:F8:10:62:34:D6:CE:CB:08:D4:1C:3A:E7:4C:4C:
  • 68:10:14:09:0F:02:21:00:FD:7A:C7:D7:3F:5E:4C:B6:
  • F7:35:6B:BA:C9:15:31:96:17:E1:A1:38:B5:26:17:21:
  • 96:28:DB:BE:61:23:48:8E

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.lynx.piyou.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.puma.piyou.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid