SurfaceMap › b › baozeqiche.com

baozeqiche.com

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

Domain & DNS

warn

20 passed 3 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2016062016 on dns10.hichina.com (139.224.142.121); 2026081813 on dns9.hichina.com (120.76.107.52); 2026082509 on dns10.hichina.com (120.76.107.51), dns10.hichina.com (120.76.107.41), dns9.hichina.com (139.224.142.122), dns9.hichina.com (120.76.107.42); 2026082616 on dns10.hichina.com (47.118.199.211), dns10.hichina.com (39.96.153.41), dns10.hichina.com (47.118.199.201), dns10.hichina.com (139.224.142.111), dns9.hichina.com (139.224.142.112), dns9.hichina.com (39.96.153.42), dns9.hichina.com (47.118.199.202), dns9.hichina.com (2408:4009:501::17); 2026082617 on dns10.hichina.com (39.96.153.51), dns10.hichina.com (2408:4009:501::18), dns9.hichina.com (39.96.153.52), dns9.hichina.com (47.118.199.212). 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 baozeqiche.com ›

Mail

fail

6 passed 6 warn 2 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 key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx.ym.163.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 111.124.200.35 (mx.ym.163.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 baozeqiche.com ›