SSL check results of flunder.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for flunder.net 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 Wed, 27 May 2020 04:00:55 +0000

The mailservers of flunder.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @flunder.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
eldar.brandur.de
2a03:4000:9:5b5:dead:beef::1
10
supported
eldar.brandur.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
eldar.brandur.de
37.221.198.103
10
supported
eldar.brandur.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

We have received emails from these servers with @flunder.net sender addresses. Test mail delivery

Host TLS Version & Cipher
eldar.brandur.de (37.221.198.103)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=eldar.brandur.de

Certificate chain
Subject
Common Name (CN)
  • eldar.brandur.de
Alternative Names
  • autoconfig.5rg.de
  • autoconfig.flunder.net
  • autoconfig.gediga.net
  • autodiscover.5rg.de
  • autodiscover.flunder.net
  • autodiscover.gediga.net
  • eldar.brandur.de
  • mail.5rg.de
  • mail.flunder.net
  • mail.gediga.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-03-10
Not valid after
2020-06-08
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
25:0B:D1:C7:77:06:FB:CE:42:99:3A:F6:22:F3:79:09:64:17:5F:BD:4B:B4:62:BE:45:F4:EA:5B:4B:9E:26:F9
SHA1
64:92:14:3F:3E:4B:B6:C5:CC:3C:69:CD:58:AC:84:A4:12:3E:4D:02
X509v3 extensions
subjectKeyIdentifier
  • 09:0D:EF:62:A8:D1:88:1E:FF:D5:B8:57:EF:7E:58:1A:B0:5C:B4:83
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
  • 4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
  • Timestamp : Mar 10 10:03:57.192 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:46:DE:C8:C5:F0:97:F8:25:A8:25:75:E4:
  • CB:E3:05:74:3A:3E:83:78:46:81:26:F6:F2:EB:C2:E1:
  • 30:70:4B:35:02:21:00:86:ED:52:BD:18:65:DB:80:37:
  • 9E:97:23:52:04:A4:C2:58:71:9D:30:9E:BC:53:B8:F9:
  • 35:CE:EB:47:EB:94:9A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Mar 10 10:03:57.190 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:84:5F:AD:51:AB:49:EB:8E:8B:47:90:
  • C8:4E:6B:32:FC:4B:13:4B:46:D2:3D:AF:4F:A1:CE:83:
  • A4:51:0E:DC:B7:02:20:6E:0F:84:83:F5:C0:49:C4:C1:
  • C8:1A:F5:05:13:46:E1:5E:3F:30:31:F5:C4:53:AE:AD:
  • BD:5A:2C:29:73:92:02

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.eldar.brandur.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid