SurfaceMap › 5 › 56ck.com

56ck.com

Checked 2026-10-22 07:33 UTC · first added 2026-10-21
✗Problems found Score 36 of 100

Domain & DNS

fail

20 passed 3 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns27.hichina.com (139.224.142.99): read udp 46.225.38.91:57554->139.224.142.99:53: i/o timeout; dns28.hichina.com (47.118.199.221): read udp 46.225.38.91:53347->47.118.199.221:53: i/o timeout; dns28.hichina.com (39.96.153.62): read udp 46.225.38.91:48310->39.96.153.62:53: i/o timeout.
    #14
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2026082509 on dns27.hichina.com (139.224.142.109), dns28.hichina.com (120.76.107.62), dns28.hichina.com (139.224.142.107); 2026082616 on dns27.hichina.com (39.96.153.39), dns27.hichina.com (120.76.107.59), dns27.hichina.com (47.118.199.199), dns27.hichina.com (39.96.153.59), dns27.hichina.com (47.118.199.219), dns28.hichina.com (39.96.153.37), dns28.hichina.com (2408:4009:501::36); 2026082617 on dns27.hichina.com (120.76.107.39), dns27.hichina.com (2408:4009:501::35), dns28.hichina.com (120.76.107.37), dns28.hichina.com (47.118.199.197); 2026082709 on dns28.hichina.com (139.224.142.102). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    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.
    #23
  • !
    Not signed
    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.
    #27

Recent checks

✗

Full report

Domain & DNS report for 56ck.com ›

Mail

fail

6 passed 5 warn 3 failed

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • ✗
    No DKIM keys published
    DKIM · _domainkey.56ck.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: mxdomain.qq.com -> mx3.qq.com
    #22
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 203.205.219.57 (mxdomain.qq.com), 240d:c040:1:40::133 (mxdomain.qq.com). Ask your hosting provider to set one.
    #30
  • !
    Not configured
    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.
    #32

Recent checks

✗

Full report

Mail report for 56ck.com ›