SurfaceMap › u › umeng.com

umeng.com

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

Domain & DNS

fail

24 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.alibabadns.com (106.11.35.19): read udp 46.225.38.91:50333->106.11.35.19:53: i/o timeout; ns2.alibabadns.cn (2401:b180:4100::2): read udp [2a01:4f8:1c1c:eebf::1]:56279->[2401:b180:4100::2]:53: i/o timeout.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.alibabadns.cn, ns2.alibabadns.cn. ns1.alibabadns.cn, ns1.alibabadns.com, ns2.alibabadns.cn, ns2.alibabadns.com report NS ns1.alibabadns.com ns2.alibabadns.com.
    #7
  • !
    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.
    #32

Recent checks

✗

Full report

Domain & DNS report for umeng.com ›

Mail

fail

19 passed 7 warn 1 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
  • !
    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.alibaba-inc.com, mxus1.alibaba-inc.com
    #11
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: mxus1.alibaba-inc.com -> mxus1.alibaba-inc.com.gds.alibabadns.com
    #22
  • !
    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_report@service.aliyun.com (needs umeng.com._report._dmarc.service.aliyun.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.48 (mx1.alibaba-inc.com), 106.11.232.179 (mxus1.alibaba-inc.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 umeng.com ›