big-direkt.de

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-188.akam.net: "41824.5"; a1-188.akam.net: "41824.8"; a11-66.akam.net: "41824.8"; a11-66.akam.net: "41824.9"; a16-66.akam.net: "48878.31"; a16-66.akam.net: "48878.32"; a18-66.akam.net: "48878.27"; a18-66.akam.net: "48878.33"; a24-64.akam.net: "48878.33"; a24-64.akam.net: "48878.29"; a3-66.akam.net: "41824.6". Hide or replace the version string.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: bgmta.in.tmes.trendmicro.eu

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.