jstv.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: vip1.alidns.com, vip2.alidns.com; only in the zone: vip3.alidns.com, vip4.alidns.com. vip1.alidns.com, vip2.alidns.com, vip3.alidns.com, vip4.alidns.com report NS vip3.alidns.com vip4.alidns.com.

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: vip1.alidns.com (glue 121.40.6.161, 140.205.1.1, 170.33.32.208, 170.33.73.24, 170.33.80.8, 2408:4009:500::1, 39.103.26.210, 47.116.84.176, 8.129.152.243, 8.212.93.1, zone 8.212.93.1, 140.205.1.1, 170.33.80.8, 170.33.73.24, 170.33.32.208, 2408:4009:500::1); vip2.alidns.com (glue 121.40.6.162, 140.205.1.2, 170.33.32.209, 170.33.73.25, 170.33.80.9, 2408:4009:500::2, 39.103.26.211, 47.116.84.177, 8.129.152.244, 8.212.93.2, zone 170.33.32.209, 170.33.80.9, 8.212.93.2, 140.205.1.2, 170.33.73.25, 2408:4009:500::2). Update the glue at your registrar.

SOA · The nameservers serve different versions of the zone: 2008080818 on vip1.alidns.com (140.205.1.1), vip2.alidns.com (8.212.93.2), vip2.alidns.com (140.205.1.2), vip2.alidns.com (170.33.73.25), vip3.alidns.com (8.212.93.3), vip3.alidns.com (170.33.73.26), vip4.alidns.com (170.33.73.27); 2026081712 on vip2.alidns.com (170.33.32.209), vip3.alidns.com (170.33.32.210); 2026081716 on vip1.alidns.com (170.33.73.24), vip2.alidns.com (170.33.80.9); 2026081810 on vip1.alidns.com (8.212.93.1), vip1.alidns.com (2408:4009:500::1), vip2.alidns.com (2408:4009:500::2), vip3.alidns.com (2408:4009:500::3), vip4.alidns.com (2408:4009:500::4); 2026082415 on vip3.alidns.com (140.205.1.5), vip4.alidns.com (140.205.1.6); 2026082516 on vip1.alidns.com (170.33.80.8), vip1.alidns.com (170.33.32.208), vip3.alidns.com (170.33.80.10), vip4.alidns.com (170.33.80.11), vip4.alidns.com (170.33.32.211), vip4.alidns.com (8.212.93.4). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

SOA · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, negative TTL 10m.

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

MX · The following MX hosts could not be resolved to IPv6 addresses: mxbiz1.qq.com, mxbiz2.qq.com

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:mailauth-reports@qq.com (needs jstv.com._report._dmarc.qq.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: 103.86.78.2 (mxbiz1.qq.com), 103.86.78.3 (mxbiz1.qq.com), 43.154.252.202 (mxbiz2.qq.com), 43.154.252.16 (mxbiz2.qq.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.