kucoin.com

Checked 22 October 2026, 09:33 UTC · via 8.8.8.8
!Passed with warnings
21 passed 8 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 +include:spf.onlarksuite.com +include:spf.email.notify.best +include:spf.email.engagelab.com +include:spf.kumail.top ~all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 9 of 10 DNS lookups #2
    SPF record needs 9 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.kucoin.com)

Found

Record
v=DMARC1; p=quarantine; fo=1;ruf=mailto:dmarc@corp.kucoin.com,mailto:dmarc@kucoin.com;rua=mailto:dmarc@corp.kucoin.com,mailto:dmarc_report@kucoin.com
Found at
_dmarc.kucoin.com
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@corp.kucoin.com,mailto:dmarc_report@kucoin.comAggregate report addresses
rufmailto:dmarc@corp.kucoin.com,mailto:dmarc@kucoin.comFailure report addresses
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@corp.kucoin.com, mailto:dmarc_report@kucoin.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector1, google

Found

Selectors
mail, selector1, google
_domainkey
NXDOMAIN
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 2048 bits
googleRSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1, google #7
    DKIM keys found for this domain with selectors: mail, selector1, google
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

9 mail servers

Found

PriorityHostRecordsReverse DNS
1spam01.kumail.topCNAME sec-prd-public-nlb-fac902a996e12b43.elb.ap-northeast-1.amazonaws.com A 54.65.240.118 A 18.176.243.155 A 54.178.221.94ec2-54-65-240-118.ap-northeast-1.compute.amazonaws.com ✓ ec2-18-176-243-155.ap-northeast-1.compute.amazonaws.com ✓ ec2-54-178-221-94.ap-northeast-1.compute.amazonaws.com ✓
1spam02.kumail.topCNAME sec-prd-public-nlb-fac902a996e12b43.elb.ap-northeast-1.amazonaws.com A 18.176.243.155 A 54.65.240.118 A 54.178.221.94ec2-18-176-243-155.ap-northeast-1.compute.amazonaws.com ✓ ec2-54-65-240-118.ap-northeast-1.compute.amazonaws.com ✓ ec2-54-178-221-94.ap-northeast-1.compute.amazonaws.com ✓
3mx1.larksuite.comA 18.139.153.173ec2-18-139-153-173.ap-southeast-1.compute.amazonaws.com ✓
5mx2.larksuite.comA 18.139.153.173ec2-18-139-153-173.ap-southeast-1.compute.amazonaws.com ✓
10mx3.larksuite.comA 18.139.153.173 A 101.126.58.223 A 122.14.230.154ec2-18-139-153-173.ap-southeast-1.compute.amazonaws.com ✓ lookup failed no PTR
20mx1.notify.bestA 159.138.104.116 A 114.119.172.164ecs-159-138-104-116.compute.hwclouds-dns.com (does not resolve back) ecs-114-119-172-164.compute.hwclouds-dns.com (does not resolve back)
50mx1.engagelab.comA 94.74.91.25 A 114.119.172.160ecs-94-74-91-25.compute.hwclouds-dns.com (does not resolve back) ecs-114-119-172-160.compute.hwclouds-dns.com (does not resolve back)
55mx.sendcloud.orgA 106.75.109.68 A 106.75.34.64mx.sendcloud.org ✓ mail.mifanwangluo.com (does not resolve back)
60mxdm-ap-southeast-1.aliyun.comA 47.246.173.111no PTR

Checks

  • ✓ 9 MX records #9
    Found 9 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    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
    #11
  • ✓ Redundant MX hosts #12
    Found 9 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 9 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • !
    Hosts are CNAMEs
    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
    #22
  • !
    Addresses without reverse DNS
    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.
    #30

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 9 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
spam01.kumail.topnone-
spam02.kumail.topnone-
mx1.larksuite.comnone-
mx2.larksuite.comnone-
mx3.larksuite.comnone-
mx1.notify.bestnone-
mx1.engagelab.comnone-
mx.sendcloud.orgnone-
mxdm-ap-southeast-1.aliyun.comnone-

Checks

  • !
    Not configured
    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.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38