mulfingen.de

Scanned 2 days ago · Aug 17, 2026, 3:29 PM

A

TLS & Certificate

Protocol support, cipher strength and the certificate chain, evaluated the way a browser would.

Score90%
  • the server accepts 2 weak cipher suite(s): ECDHE-RSA-AES256-SHA384, ECDHE-RSA-AES128-SHA256
NegotiatedTLSv1.3, TLS_AES_256_GCM_SHA384
Forward secrecyYes
HSTSenabled, max-age=31536000

Protocol support

YesTLS 1.3
YesTLS 1.2
NoTLS 1.1 (deprecated)
NoTLS 1.0 (deprecated)

Cipher suites probed

Each suite below was tested with its own TLS 1.2 handshake, restricted to exactly that cipher - “accepted” means the server completed a handshake using it, not merely that it's listed as a possibility.

ECDHE-ECDSA-AES256-GCM-SHA384
SecureNot offered
ECDHE-RSA-AES256-GCM-SHA384
SecureAccepted
ECDHE-ECDSA-AES128-GCM-SHA256
SecureNot offered
ECDHE-RSA-AES128-GCM-SHA256
SecureAccepted
ECDHE-ECDSA-CHACHA20-POLY1305
SecureNot offered
ECDHE-RSA-CHACHA20-POLY1305
SecureNot offered
DHE-RSA-AES256-GCM-SHA384
SecureAccepted
DHE-RSA-AES128-GCM-SHA256
SecureAccepted
ECDHE-RSA-AES256-SHA384
WeakAccepted
ECDHE-RSA-AES128-SHA256
WeakAccepted
AES256-GCM-SHA384
WeakNot offered
AES128-GCM-SHA256
WeakNot offered
DES-CBC3-SHA
InsecureNot offered
RC4-SHA
InsecureNot offered
NULL-SHA
InsecureNot offered

Certificate

Subjectmulfingen.de
IssuerYR1
Additional namesmulfingen.de, www.mulfingen.de
ValidJul 15, 2026, 11:29 PM – Oct 13, 2026, 11:29 PM (expires in 57 days)
KeyRSA 2048 bit
Certificate chain4 certificate(s)
Trusted by common trust storesYes
Matches the scanned hostnameYes
Self-signedNo
F

Security Headers

The HTTP response headers browsers use to restrict what a page - or an attacker inside it - can do.

Score25%
  • no Content-Security-Policy header
  • no X-Content-Type-Options: nosniff
  • no clickjacking protection (X-Frame-Options or frame-ancestors)
  • no Referrer-Policy header
  • no Permissions-Policy header
  • no Cross-Origin-Opener-Policy header
  • no Cross-Origin-Resource-Policy header
  • the Server header discloses "nginx"
Content-Security-Policynot set
Strict-Transport-Securitymax-age=31536000
X-Content-Type-Optionsnot set
X-Frame-Optionsnot set
Referrer-Policynot set
Permissions-Policynot set
Cross-Origin-Opener-Policynot set
Cross-Origin-Resource-Policynot set
A

Email

Whether mail delivered to this domain is protected in transit, and whether SPF/DMARC stop it being spoofed.

Score90%
  • port 25 was not reachable on any mail server from our scanner (commonly blocked by cloud providers) - mail transport security could not be verified
  • the DMARC policy is "none" (monitoring only, not enforced)
SPFv=spf1 mx include:spf.protect.kvnbw.de ~all
DMARCv=DMARC1; p=none; pct=100; sp=none; aspf=r; adkim=r;

Mail servers

mx6.kvnbw.denot reachable on port 25 from our scanner
mx7.kvnbw.denot reachable on port 25 from our scanner
mx8.kvnbw.denot reachable on port 25 from our scanner