SurfaceMap › w › wondershare.com

wondershare.com

Checked 2026-10-22 11:32 UTC · first added 2026-10-21
✗Problems found Score 47 of 100

Domain & DNS

warn

22 passed 4 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: vip3.alidns.com (glue 121.40.6.163, 140.205.1.5, 170.33.32.210, 170.33.73.26, 170.33.80.10, 2408:4009:500::3, 39.103.26.212, 47.108.36.163, 47.116.84.178, 8.129.152.245, 8.212.93.3, zone 140.205.1.5, 170.33.32.210, 170.33.80.10, 8.212.93.3, 170.33.73.26, 2408:4009:500::3); vip4.alidns.com (glue 121.40.6.164, 140.205.1.6, 170.33.32.211, 170.33.73.27, 170.33.80.11, 2408:4009:500::4, 39.103.26.213, 47.108.36.164, 47.116.84.179, 8.129.152.246, 8.212.93.4, zone 8.212.93.4, 170.33.73.27, 170.33.80.11, 170.33.32.211, 140.205.1.6, 2408:4009:500::4). Update the glue at your registrar.
    #8
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2026081316 on vip3.alidns.com (8.212.93.3); 2026081716 on vip3.alidns.com (170.33.32.210), vip4.alidns.com (170.33.80.11); 2026081810 on vip3.alidns.com (170.33.73.26), vip3.alidns.com (2408:4009:500::3), vip4.alidns.com (8.212.93.4), vip4.alidns.com (170.33.32.211); 2026082415 on vip3.alidns.com (140.205.1.5), vip4.alidns.com (140.205.1.6), vip4.alidns.com (2408:4009:500::4); 2026082516 on vip3.alidns.com (170.33.80.10), vip4.alidns.com (170.33.73.27). 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 wondershare.com ›

Mail

fail

19 passed 7 warn 2 failed

Areas

✓SPF ✗DMARC !DKIM !DNSSEC !MX !TLS ✗BIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✗
    DMARC not strict enough for BIMI
    BIMI · Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.
    #39
  • !
    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: mx1.qiye.aliyun.com, mxn.mxhichina.com, mxw.mxhichina.com
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), dkim (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 47.246.167.188 (mx1.qiye.aliyun.com), 47.246.137.47 (mxn.mxhichina.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
  • !
    No certificate (a=)
    BIMI · The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38

Recent checks

✗

Full report

Mail report for wondershare.com ›