SSL-Tools

SSL check results of mail.feuerwehr-verden.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.feuerwehr-verden.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 Fri, 17 May 2024 04:27:59 +0000

The mailservers of mail.feuerwehr-verden.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.feuerwehr-verden.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.feuerwehr-verden.de
162.55.93.58
 -
supported
feuerwehr-verden.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.feuerwehr-verden.de
2a01:4f8:271:5715::3
 -
supported
feuerwehr-verden.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

We have not received any emails from a @mail.feuerwehr-verden.de address so far. Test mail delivery

Certificates

First seen at:

CN=feuerwehr-verden.de

Certificate chain
  • feuerwehr-verden.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • feuerwehr-verden.de
Alternative Names
  • *.feuerwehr-verden.de
  • feuerwehr-verden.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-13
Not valid after
2024-08-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8D:FE:FD:1A:7A:7A:4A:29:53:0F:D0:9B:1C:B0:43:9C:93:6F:37:AE:C8:F8:D3:74:D4:33:C8:5A:20:7E:4F:BD
SHA1
D9:0D:57:69:EE:D6:58:FA:82:02:BB:E3:43:9A:2A:36:9E:EE:20:24
X509v3 extensions
subjectKeyIdentifier
  • A9:BC:77:90:BF:02:48:C4:7E:9A:3D:7A:74:52:68:E6:C1:8E:5B:42
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : May 13 07:04:49.827 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B4:8D:94:43:80:D3:90:81:90:EB:9F:
  • 28:F9:98:23:13:EC:0D:F9:9A:0C:36:8B:67:E1:24:84:
  • EF:0B:AC:4B:B7:02:20:3A:9E:3F:8B:37:2D:E0:5A:CC:
  • BA:08:A4:DA:E7:18:9D:EB:E4:C9:DF:77:AE:EB:ED:16:
  • 8D:61:63:96:E5:E5:0B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : May 13 07:04:50.026 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5D:84:EA:1F:A8:12:7C:C9:CC:7F:8B:1A:
  • D5:B8:1E:8A:5F:9B:3A:CA:3C:8B:50:C8:5C:6B:41:70:
  • 6B:2C:09:DC:02:21:00:E1:08:11:E3:96:6E:6B:C2:8F:
  • DA:B4:EC:69:24:D5:3C:75:7C:2E:44:D7:81:31:63:D5:
  • 08:C0:72:D7:A4:25:09