SSL-Tools

SSL check results of mx1.1fire.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mx1.1fire.de 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 Sun, 03 Aug 2025 01:37:55 +0000

The mailservers of mx1.1fire.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mx1.1fire.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.1fire.de
82.153.225.6
 -
supported
mx1.1fire.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mx1.1fire.de
2a06:de00:1f00:1010::3a17
 -
supported
mx1.1fire.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @mx1.1fire.de address so far. Test mail delivery

Certificates

First seen at:

CN=mx1.1fire.de

Certificate chain
  • mx1.1fire.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx1.1fire.de
Alternative Names
  • autoconfig.1fire.de
  • autoconfig.1fire.host
  • autoconfig.1fsrv.de
  • autodiscover.1fire.de
  • autodiscover.1fire.host
  • autodiscover.1fsrv.de
  • mx1.1fire.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-21
Not valid after
2025-09-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1C:61:5F:79:7C:CF:C7:08:BF:DC:7B:E3:B0:57:48:A0:18:A0:48:FD:71:D1:F9:E9:41:7C:46:66:95:75:1A:A8
SHA1
84:96:D4:5B:3B:12:53:8A:F8:43:B0:E3:4A:D0:1E:E4:6D:CF:DE:E9
X509v3 extensions
subjectKeyIdentifier
  • 32:E1:8A:DF:C7:43:D8:AA:6F:2E:A0:D1:8C:60:43:AB:27:7A:DB:1D
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 : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Jun 21 21:02:20.670 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CF:45:EB:BA:88:4A:03:32:40:AF:E9:
  • 7D:E7:5B:7E:73:41:F3:3A:D6:7D:D5:1F:2E:35:0C:60:
  • 3F:B7:29:C6:6D:02:21:00:EA:4A:EB:4D:8A:E2:2A:5D:
  • 37:C5:21:83:24:D7:A9:BA:A7:4B:A0:5C:9F:06:9B:07:
  • EB:1D:E0:E6:31:A2:49:82
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : Jun 21 21:02:21.242 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A7:11:81:29:C6:49:DB:37:A0:BD:A7:
  • 7D:B9:B5:14:D3:3A:7D:44:01:C8:6A:FE:52:42:2D:87:
  • 37:6C:41:58:C4:02:21:00:F0:EA:03:8D:5E:F0:7A:B7:
  • 71:06:8F:56:88:9D:56:1B:A2:F1:1B:EC:19:B2:B3:AF:
  • DE:60:91:DD:6E:89:CF:E5