kucoin.com

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: A (1m). Low TTLs are useful just before a planned change.

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: spam01.kumail.top, spam02.kumail.top, mx1.larksuite.com, mx2.larksuite.com, mx3.larksuite.com, mx1.notify.best, mx1.engagelab.com, mx.sendcloud.org, mxdm-ap-southeast-1.aliyun.com

MX · Found 9 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

MX · MX records must point to a host name with A/AAAA records, not to a CNAME: spam01.kumail.top -> sec-prd-public-nlb-fac902a996e12b43.elb.ap-northeast-1.amazonaws.com, spam02.kumail.top -> sec-prd-public-nlb-fac902a996e12b43.elb.ap-northeast-1.amazonaws.com

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

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 122.14.230.154 (mx3.larksuite.com), 47.246.173.111 (mxdm-ap-southeast-1.aliyun.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.