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 Fri, 10 Jan 2025 22:15:24 +0000

The mailservers of firsching.me can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
srv01.firsching.me
2001:678:594:594::85
 10
supported
srv01.firsching.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
srv01.firsching.me
93.88.225.85
 10
supported
srv01.firsching.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 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=srv01.firsching.me

Certificate chain
  • srv01.firsching.me
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • srv01.firsching.me
Alternative Names
  • srv01.firsching.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-12-02
Not valid after
2025-03-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
45:55:47:4D:13:0B:B9:B4:B5:07:D8:BF:E9:C3:9B:81:AA:40:4E:9A:C5:A2:3F:D8:F7:F1:DC:DC:54:96:78:53
SHA1
CB:F0:82:FC:96:80:EB:E7:69:7C:D9:2C:17:37:BC:5D:9E:0E:D2:1A
X509v3 extensions
subjectKeyIdentifier
  • 7F:70:7C:1F:7F:73:1F:A9:0C:64:B0:31:28:3D:98:05:1E:B8:A0:89
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Dec 2 23:36:20.135 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:60:9F:AC:63:08:9D:C3:C1:98:E6:B9:D7:
  • 05:DF:A5:80:43:D7:2C:EA:2E:13:E2:03:88:78:09:58:
  • 4C:B5:04:FD:02:21:00:CD:BC:7B:FE:FB:22:60:64:9A:
  • AE:2B:49:C6:1C:D4:18:C5:67:75:73:CB:86:3A:80:67:
  • 49:04:0B:0B:06:CB:DD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Dec 2 23:36:20.185 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C5:8E:E0:20:99:84:50:CF:40:92:0C:
  • 42:66:AD:22:94:65:F4:35:8C:55:A6:62:15:E0:AC:64:
  • C4:CC:92:60:A7:02:20:4C:35:3A:90:2E:62:C4:BA:BD:
  • E2:EB:76:7E:5A:14:57:20:1B:AC:2C:31:63:D2:ED:E6:
  • 77:8C:D9:37:BD:9E:B1