SurfaceMap › o › oclean.com

oclean.com

Checked 2026-10-22 10:05 UTC · first added 2026-10-21
✗Problems found Score 43 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: dns9.hichina.com (120.76.107.52): read udp 46.225.38.91:42800->120.76.107.52:53: i/o timeout.
    #14
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2016080418 on dns10.hichina.com (139.224.142.121), dns10.hichina.com (139.224.142.111); 2026082509 on dns10.hichina.com (120.76.107.41), dns10.hichina.com (120.76.107.51), dns9.hichina.com (139.224.142.122), dns9.hichina.com (120.76.107.42), dns9.hichina.com (2408:4009:501::17); 2026082616 on dns10.hichina.com (47.118.199.201), dns10.hichina.com (47.118.199.211), dns10.hichina.com (2408:4009:501::18), dns9.hichina.com (47.118.199.202), dns9.hichina.com (39.96.153.42), dns9.hichina.com (139.224.142.112), dns9.hichina.com (39.96.153.52); 2026082617 on dns10.hichina.com (39.96.153.41), dns10.hichina.com (39.96.153.51), 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 oclean.com ›

Mail

fail

19 passed 6 warn 2 failed

Areas

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

Problems

  • ✗
    14 DNS lookups, over the limit of 10
    SPF · SPF record needs 14 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    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: mxbiz1.qq.com, mxbiz2.qq.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (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:mailauth-reports@qq.com (needs oclean.com._report._dmarc.qq.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: 103.86.78.3 (mxbiz1.qq.com), 103.86.78.2 (mxbiz1.qq.com), 43.154.252.16 (mxbiz2.qq.com), 43.154.252.202 (mxbiz2.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 oclean.com ›