SurfaceMap › q › qq.com

qq.com

Checked 2026-10-22 10:23 UTC · first added 2026-10-21
✗Problems found Score 62 of 100

Domain & DNS

fail

24 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

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: ns1.qq.com (112.90.13.140): dial tcp 112.90.13.140:53: i/o timeout; ns1.qq.com (183.60.116.2): dial tcp 183.60.116.2:53: i/o timeout; ns1.qq.com (2402:4e00:c050:7a00::3): dial tcp [2402:4e00:c050:7a00::3]:53: i/o timeout; ns2.qq.com (1.12.96.10): dial tcp 1.12.96.10:53: i/o timeout; ns2.qq.com (240e:974:e600:3ee::2): dial tcp [240e:974:e600:3ee::2]:53: i/o timeout; ns3.qq.com (120.204.7.98): dial tcp 120.204.7.98:53: i/o timeout.
    #19
  • !
    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 5m, expire 1d, negative TTL 5m.
    #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 qq.com ›

Mail

fail

22 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.qq.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 203.205.219.57 (mx3.qq.com), 240d:c040:1:40::133 (mx3.qq.com), 58.254.165.118 (mx2.qq.com), 58.254.165.82 (mx2.qq.com), 157.255.221.247 (mx2.qq.com), 157.255.4.241 (mx2.qq.com), 240e:97c:2f:1003::34 (mx2.qq.com), 240e:97c:2f:1001::1b (mx2.qq.com), 240e:97c:2f::1c (mx2.qq.com), 2408:8756:3af0:3009::126 (mx2.qq.com), 240e:97c:2f:1001::14 (mx2.qq.com), 162.62.116.184 (mx1.qq.com), 2408:8756:f50:200f::12a (mx1.qq.com), 2408:8756:f50:1::63 (mx1.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 qq.com ›