Identity
12
F
dnsv4.com
Posture Score: 29/100
Scanned May 29, 2026 at 8:52 PM UTC
Score History
Attack Surface
19
Reputation
55
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.dnsv4.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@dnsv4.com").
No STARTTLS support on mxbiz1.qq.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
FCrDNS failure: no PTR for 103.86.78.2 (mxbiz1.qq.com)
The IP 103.86.78.2 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 103.86.78.3 (mxbiz1.qq.com)
The IP 103.86.78.3 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.
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.dnsv4.com
No PTR record for MX IP: 103.86.78.2
The IP 103.86.78.2 (for mxbiz1.qq.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 103.86.78.3
The IP 103.86.78.3 (for mxbiz1.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.dnsv4.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.
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@dnsv4.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.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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.
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 mxbiz1.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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 1765163637, Refresh: 3600s, Retry: 180s, Expire: 1209600s, Min TTL: 180s
Attack Surface Findings
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Non-responsive IP for ns1.dnsv4.com: 36.155.149.53
The subdomain ns1.dnsv4.com resolves to 36.155.149.53 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 36.155.149.53 is operational or remove the DNS record for ns1.dnsv4.com.
Non-responsive IP for ns1.dnsv4.com: 43.134.249.54
The subdomain ns1.dnsv4.com resolves to 43.134.249.54 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 43.134.249.54 is operational or remove the DNS record for ns1.dnsv4.com.
Non-responsive IP for ns1.dnsv4.com: 117.89.178.53
The subdomain ns1.dnsv4.com resolves to 117.89.178.53 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 117.89.178.53 is operational or remove the DNS record for ns1.dnsv4.com.
Non-responsive IP for ns1.dnsv4.com: 1.13.76.53
The subdomain ns1.dnsv4.com resolves to 1.13.76.53 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 1.13.76.53 is operational or remove the DNS record for ns1.dnsv4.com.
Non-responsive IP for ns1.dnsv4.com: 1.12.0.24
The subdomain ns1.dnsv4.com resolves to 1.12.0.24 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 1.12.0.24 is operational or remove the DNS record for ns1.dnsv4.com.
Non-responsive IP for ns1.dnsv4.com: 125.94.59.153
The subdomain ns1.dnsv4.com resolves to 125.94.59.153 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 125.94.59.153 is operational or remove the DNS record for ns1.dnsv4.com.
Non-responsive IP for ns1.dnsv4.com: 1.12.0.25
The subdomain ns1.dnsv4.com resolves to 1.12.0.25 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 1.12.0.25 is operational or remove the DNS record for ns1.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 1.12.0.26
The subdomain ns2.dnsv4.com resolves to 1.12.0.26 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 1.12.0.26 is operational or remove the DNS record for ns2.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 43.130.172.54
The subdomain ns2.dnsv4.com resolves to 43.130.172.54 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 43.130.172.54 is operational or remove the DNS record for ns2.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 117.135.128.153
The subdomain ns2.dnsv4.com resolves to 117.135.128.153 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 117.135.128.153 is operational or remove the DNS record for ns2.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 111.13.203.53
The subdomain ns2.dnsv4.com resolves to 111.13.203.53 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 111.13.203.53 is operational or remove the DNS record for ns2.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 163.177.5.53
The subdomain ns2.dnsv4.com resolves to 163.177.5.53 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 163.177.5.53 is operational or remove the DNS record for ns2.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 1.12.0.23
The subdomain ns2.dnsv4.com resolves to 1.12.0.23 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 1.12.0.23 is operational or remove the DNS record for ns2.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 220.196.136.53
The subdomain ns2.dnsv4.com resolves to 220.196.136.53 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 220.196.136.53 is operational or remove the DNS record for ns2.dnsv4.com.
Non-responsive IP for ns2.dnsv4.com: 101.227.168.53
The subdomain ns2.dnsv4.com resolves to 101.227.168.53 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 101.227.168.53 is operational or remove the DNS record for ns2.dnsv4.com.
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.
DNS ANY query returns 4 record(s)
The DNS server responds to ANY queries with 4 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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 email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
4 subdomain(s) discovered for dnsv4.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 dnsv4.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.dnsv4.com, resolving to 113.96.208.81. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Reputation Findings
Listed on dnsbl.spfbl.net
103.86.78.3 (mxbiz1.qq.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
103.86.78.2 (mxbiz1.qq.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Could not retrieve TLS certificate
Failed to connect to dnsv4.com:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
Domain valid for 2702 days
Domain dnsv4.com expires on 2033-10-22.
Domain transfer and delete locks enabled
Domain dnsv4.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for dnsv4.com do not match known disposable email provider patterns.
Domain is 5698 days old
Domain dnsv4.com was registered 2010-10-22.
No wildcard MX records
No wildcard MX records detected for dnsv4.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mxbiz1.qq.com) uses with cipher including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (bizmx54.qq.com) aligns with the MX hostname (mxbiz1.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 dnsv4.com
HTTPS request to https://dnsv4.com failed or timed out.
Could not connect to webmail.dnsv4.com
HTTPS request to https://webmail.dnsv4.com failed or timed out.
WHOIS registration data
Registrar: DNSPod, Inc. | Created: 2010-10-22 | Expires: 2033-10-22 | Updated: 2024-09-10
WHOIS privacy protection not detected
Domain dnsv4.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: dns4.com (has MX!), nsv4.com, dsv4.com, dnv4.com
4 registered lookalike domain(s) that could be used for phishing against your brand. 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 missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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 missing
⚠️ 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: mxbiz1.qq.com
PTR record proves mail server legitimacy
MX: mxbiz1.qq.com
Mail server at 103.86.78.3
→
PTR Record
No PTR record
⚠️ Mail server mxbiz1.qq.com (103.86.78.3) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mxbiz1.qq.com
RBL check ensures server is not blacklisted
MX: mxbiz1.qq.com
Mail server at 103.86.78.3
→
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 not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
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/dnsv4.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan dnsv4.com Again