SurfaceMap › x › xiami.com

xiami.com

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

Domain & DNS

fail

24 passed 3 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns6.taobao.com (2401:b180:4100::6): dial tcp [2401:b180:4100::6]:53: i/o timeout.
    #19
  • !
    Unusual SOA timers
    SOA · expire 1h is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1h must be longer than refresh + retry. Current values: refresh 1h, retry 20m, expire 1h, negative TTL 6m.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 3h; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for xiami.com ›

Mail

fail

19 passed 6 warn 2 failed

Areas

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

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
  • ✗
    Multiple SPF records
    SPF · Found 5 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • !
    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: mxn.mxhichina.com, mxw.mxhichina.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc_alibaba@service.alibaba.com (needs xiami.com._report._dmarc.service.alibaba.com). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 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

Recent checks

✗

Full report

Mail report for xiami.com ›