SSL-Tools

SSL check results of firsching.me

NEW You can also bulk check multiple servers.

Discover if the mail servers for firsching.me 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, 02 Dec 2025 11:30:38 +0000

The mailservers of firsching.me can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @firsching.me addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.firsching.me
2001:678:594:20::15
 10
supported
mail.firsching.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
53 s
mail.firsching.me
93.88.225.85
 10
supported
mail.firsching.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
55 s

Outgoing Mails

We have received emails from these servers with @firsching.me sender addresses. Test mail delivery

Host TLS Version & Cipher
unknown (93.88.225.90)
TLSv1.3 TLS_AES_256_GCM_SHA384
srv.firsching.me (IPv6:2001:678:594:594::10)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.firsching.me

Certificate chain
  • mail.firsching.me
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Expired
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.firsching.me
Alternative Names
  • mail.firsching.me
  • webmail.firsching.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-02
Not valid after
2025-08-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1A:02:65:AC:AE:91:43:87:E5:AF:39:82:27:A6:F3:F6:75:01:54:33:DB:C2:1B:2A:A4:71:AF:F5:A6:9E:64:ED
SHA1
6E:EA:B1:F3:AC:85:34:C9:34:0D:3D:94:36:FB:85:F1:91:06:F0:9F
X509v3 extensions
subjectKeyIdentifier
  • DF:36:93:41:AC:9E:9E:8F:B0:AF:24:8C:90:F4:A2:E2:CC:CA:00:F5
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/126.crl
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 : Jun 2 12:05:36.349 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3F:FB:9A:4E:A1:47:AB:E8:37:B1:B7:CB:
  • 11:2B:12:FF:73:DF:8A:E9:CA:33:72:30:B6:64:D0:5C:
  • F7:69:A8:53:02:20:1B:2F:F7:F7:64:F4:E0:D2:4E:56:
  • AB:FA:60:2C:58:A6:F0:C0:C3:52:AE:82:8D:42:0C:C6:
  • 62:B6:8D:DB:9D:FC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Jun 2 12:05:36.446 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:93:DB:3E:56:AD:01:F2:BE:5C:6A:7A:
  • F3:97:DF:4B:A3:D6:9A:55:08:1D:1C:E2:EB:66:A9:71:
  • 73:03:0F:31:18:02:20:6B:A6:0B:7E:0E:13:F6:47:86:
  • 52:37:B2:E4:34:8C:B9:82:52:D0:18:E2:7A:D5:6F:FF:
  • BF:4B:CF:AF:A2:01:D9