shanghairanking.com

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns13.xincache.com (glue 1.12.0.4, 112.80.181.45, 117.89.178.173, 129.211.176.209, 2402:4e00:1470:2::e, 36.155.149.180, zone 36.155.149.180, 117.89.178.173, 125.94.59.210, 112.80.181.45, 1.12.0.4, 129.211.176.209, 2402:4e00:1730::e, 2402:4e00:1470:2::e); ns14.xincache.com (glue 1.12.0.1, 112.80.181.111, 117.89.178.184, 129.211.176.239, 2402:4e00:111:fff::c, 36.155.149.176, zone 129.211.176.239, 36.155.149.176, 117.89.178.184, 1.12.0.1, 163.177.5.23, 112.80.181.111, 2402:4e00:111:fff::c). Update the glue at your registrar.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns13.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns14.xincache.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: qiye163mx01.mxmail.netease.com, qiye163mx02.mxmail.netease.com

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (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.