yuque.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.alipay.com: "Adns 1.0"; ns2.alipay.com: "Adns 1.0"; ns3.alipay.com: "Adns 1.0"; ns4.alipay.com: "Adns 1.0". Hide or replace the version string.

SOA · The nameservers serve different versions of the zone: 2207272122 on ns4.alipay.com (47.103.166.30); 2406071321 on ns1.alipay.com (47.102.234.254); 2610081528 on ns1.alipay.com (47.113.165.254), ns1.alipay.com (47.113.165.222), ns1.alipay.com (2400:b200:4100:6666::a), ns2.alipay.com (110.76.21.66), ns2.alipay.com (2400:b200:4100:8888::a), ns3.alipay.com (110.76.21.88), ns3.alipay.com (2400:b200:4101:6666::a), ns4.alipay.com (47.118.234.180), ns4.alipay.com (2400:b200:4101:8888::a). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

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.

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: mxn.mxhichina.com, mxw.mxhichina.com

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc_ay@service.alibaba.com (needs yuque.com._report._dmarc.service.alibaba.com). Ask the report provider to publish the record, or check the address.

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 47.246.137.47 (mxn.mxhichina.com). Ask your hosting provider to set one.

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.