segmentfault.com

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns3.dnsv3.com (glue 1.12.0.27, 101.227.168.54, 163.177.5.54, 220.196.136.54, 2402:4e00:1470:2::11, 36.155.149.55, 43.130.172.55, 43.140.78.54, 49.7.107.154, zone 43.140.78.54, 101.227.168.54, 220.196.136.54, 36.155.149.54, 43.130.172.55, 1.12.0.27, 49.7.107.154, 163.177.5.54, 2402:4e00:1470:2::11). Update the glue at your registrar.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns3.dnsv3.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv3.com: "DNSPod AUTHORITY DNS 7.3.2512.01". Hide or replace the version string.

SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.

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.

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

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: hzmx01.mxmail.netease.com, hzmx02.mxmail.netease.com

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.

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.