Identity
0
D
qq.com
Posture Score: 63/100
Scanned May 27, 2026 at 11:49 AM UTC
Score History
Attack Surface
92
Reputation
96
Identity Findings
FCrDNS failure: no PTR for 58.254.165.82 (mx2.qq.com)
The IP 58.254.165.82 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 58.254.165.118 (mx2.qq.com)
The IP 58.254.165.118 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 157.255.221.247 (mx2.qq.com)
The IP 157.255.221.247 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 157.255.4.241 (mx2.qq.com)
The IP 157.255.4.241 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 162.62.116.184 (mx1.qq.com)
The IP 162.62.116.184 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 203.205.219.57 (mx3.qq.com)
The IP 203.205.219.57 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
Nameserver unresponsive: ns3.qq.com
The nameserver ns3.qq.com is not responding on port 53.
💡 Verify that ns3.qq.com is properly configured and accessible.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.qq.com
No PTR record for MX IP: 58.254.165.82
The IP 58.254.165.82 (for mx2.qq.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 58.254.165.118
The IP 58.254.165.118 (for mx2.qq.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 157.255.221.247
The IP 157.255.221.247 (for mx2.qq.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 157.255.4.241
The IP 157.255.4.241 (for mx2.qq.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 162.62.116.184
The IP 162.62.116.184 (for mx1.qq.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 203.205.219.57
The IP 203.205.219.57 (for mx3.qq.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.qq.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
SOA expire value too short
The SOA expire value is 86400s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.
💡 Increase the SOA expire value to at least 604800 seconds (7 days).
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@qq.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
No PTR record for IPv6 address: 240e:97c:2f:1001::1b
The IPv6 address 240e:97c:2f:1001::1b for mx2.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 240e:97c:2f::1c
The IPv6 address 240e:97c:2f::1c for mx2.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 240e:97c:2f:1003::34
The IPv6 address 240e:97c:2f:1003::34 for mx2.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 2408:8756:3af0:3009::126
The IPv6 address 2408:8756:3af0:3009::126 for mx2.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 240e:97c:2f:1001::14
The IPv6 address 240e:97c:2f:1001::14 for mx2.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 2408:8756:f50:1::63
The IPv6 address 2408:8756:f50:1::63 for mx1.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 2408:8756:f50:200f::12a
The IPv6 address 2408:8756:f50:200f::12a for mx1.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 240d:c040:1:40::133
The IPv6 address 240d:c040:1:40::133 for mx3.qq.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
Slow DNS response from ns2.qq.com: 2227.4ms
The nameserver ns2.qq.com responded in 2227.4ms, exceeding the 2000ms threshold.
💡 Investigate network latency or performance issues on ns2.qq.com.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (35 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
Subdomains protected (sp=quarantine)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx2.qq.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 4 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1330914143, Refresh: 3600s, Retry: 300s, Expire: 86400s, Min TTL: 300s
Attack Surface Findings
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
25 subdomain(s) discovered for qq.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for qq.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing Strict-Transport-Security on qq.com
The Strict-Transport-Security header is not set on https://qq.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://qq.com/.well-known/security.txt.
TLS certificate valid for 184 days
Certificate for qq.com expires on 2026-11-27.
Certificate issued by DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1
The certificate for qq.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for qq.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for qq.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for qq.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on qq.com.
Domain valid for 2982 days
Domain qq.com expires on 2034-07-27.
Domain transfer and delete locks enabled
Domain qq.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for qq.com do not match known disposable email provider patterns.
Domain is 11346 days old
Domain qq.com was registered 1995-05-04.
No wildcard MX records
No wildcard MX records detected for qq.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mx3.qq.com) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (newxmmxszc69-0.qq.com) aligns with the MX hostname (mx3.qq.com).
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.qq.com
HTTPS request to https://webmail.qq.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd. | Created: 1995-05-04 | Expires: 2034-07-27 | Updated: 2026-05-22
WHOIS privacy protection not detected
Domain qq.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: aq.com (has MX!), qa.com (has MX!), qq.org (has MX!), wq.com, qw.com
15 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 15. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: quarantine
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: quarantine
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: mx2.qq.com
PTR record proves mail server legitimacy
MX: mx2.qq.com
Mail server at 58.254.165.82
→
PTR Record
No PTR record
⚠️ Mail server mx2.qq.com (58.254.165.82) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx1.qq.com
PTR record proves mail server legitimacy
MX: mx1.qq.com
Mail server at 162.62.116.184
→
PTR Record
No PTR record
⚠️ Mail server mx1.qq.com (162.62.116.184) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx3.qq.com
PTR record proves mail server legitimacy
MX: mx3.qq.com
Mail server at 203.205.219.57
→
PTR Record
No PTR record
⚠️ Mail server mx3.qq.com (203.205.219.57) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mx2.qq.com
RBL check ensures server is not blacklisted
MX: mx2.qq.com
Mail server at 58.254.165.82
→
RBL Status
Not blacklisted
Mail Server Reputation: mx1.qq.com
RBL check ensures server is not blacklisted
MX: mx1.qq.com
Mail server at 162.62.116.184
→
RBL Status
Not blacklisted
Mail Server Reputation: mx3.qq.com
RBL check ensures server is not blacklisted
MX: mx3.qq.com
Mail server at 203.205.219.57
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✗
DNSSEC
✗
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/qq.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan qq.com Again