softpedia.com

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.softpedia.com: "0.0"; ns1.softpedia.com: "0.0"; ns2.softpedia.com: "0.0"; ns3.softpedia.com: "0.0". 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.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

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: mail.softpedia.com, mail2.softpedia.com, mail3.softpedia.com

DMARC · DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.

TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".