qq.com

Checked 22 October 2026, 10:24 UTC · via 8.8.8.8
✗Problems found
22 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.mail.qq.com ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 8 of 10 DNS lookups #2
    SPF record needs 8 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.qq.com)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:mailauth-reports@qq.com
Found at
_dmarc.qq.com
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:mailauth-reports@qq.comAggregate report addresses

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:mailauth-reports@qq.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _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

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mx3.qq.comA 203.205.219.57 AAAA 240d:c040:1:40::133no PTR no PTR
20mx2.qq.comA 58.254.165.118 A 58.254.165.82 A 157.255.221.247 A 157.255.4.241 AAAA 240e:97c:2f:1003::34 AAAA 240e:97c:2f:1001::1b AAAA 240e:97c:2f::1c AAAA 2408:8756:3af0:3009::126 AAAA 240e:97c:2f:1001::14no PTR no PTR no PTR no PTR no PTR no PTR no PTR no PTR no PTR
30mx1.qq.comA 162.62.116.184 AAAA 2408:8756:f50:200f::12a AAAA 2408:8756:f50:1::63no PTR no PTR no PTR

Checks

  • ✓ 3 MX records #9
    Found 3 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • !
    Addresses without reverse DNS
    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

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 3 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx3.qq.comnone-
mx2.qq.comnone-
mx1.qq.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38