Identity
0
F
dhgate.com
Posture Score: 55/100
Scanned May 30, 2026 at 10:58 AM UTC
Attack Surface
95
Reputation
69
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.dhgate.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@dhgate.com").
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
FCrDNS failure: no PTR for 101.126.58.225 (mx2.feishu.cn)
The IP 101.126.58.225 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 122.14.229.0 (mx2.feishu.cn)
The IP 122.14.229.0 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 122.14.229.0 (mx3.feishu.cn)
The IP 122.14.229.0 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 101.126.58.225 (mx3.feishu.cn)
The IP 101.126.58.225 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.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
No PTR record for MX IP: 101.126.58.225
The IP 101.126.58.225 (for mx2.feishu.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 122.14.229.0
The IP 122.14.229.0 (for mx2.feishu.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 122.14.229.0
The IP 122.14.229.0 (for mx3.feishu.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 101.126.58.225
The IP 101.126.58.225 (for mx3.feishu.cn) 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.dhgate.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.
Generic ISP PTR hostname: ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com
The PTR record for 52.220.106.220 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.dhgate.com
Generic ISP PTR hostname: ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com
The PTR record for 52.220.106.220 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.dhgate.com
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@dhgate.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.
Shared IP 101.126.58.225 used by multiple MX servers
The IP 101.126.58.225 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 122.14.229.0 used by multiple MX servers
The IP 122.14.229.0 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 52.220.106.220 used by multiple MX servers
The IP 52.220.106.220 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on TXT records: 60s
12 TXT records have a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 60s
The SPF record has a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (43 bytes)
SPF record is within safe DNS packet size limits.
DKIM records are valid
DKIM records found and validated for selectors: google
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
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.
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 mx2.feishu.cn
Detected open mail-related ports: 25
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
MX IPs span 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1560509521, Refresh: 14400s, Retry: 7200s, Expire: 1209600s, Min TTL: 3600s
Attack Surface Findings
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.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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.
7 subdomain(s) discovered for dhgate.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 dhgate.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.dhgate.com, resolving to 43.174.250.59. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Reputation Findings
Listed on dnsbl-3.uceprotect.net
101.126.58.225 (mx3.feishu.cn) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
SMTP banner mismatch: n105-033-069
The SMTP banner identifies as 'n105-033-069' but the MX hostname is 'mx1.feishu.cn' and PTR resolves to 'ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mx1.feishu.cn).
Missing Strict-Transport-Security on dhgate.com
The Strict-Transport-Security header is not set on https://dhgate.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Wildcard MX records detected
Domain dhgate.com has wildcard MX records, which can be abused for spam or phishing.
💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.
HSTS enabled with preload on webmail.dhgate.com
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
security.txt present
Found security.txt at https://dhgate.com/.well-known/security.txt.
TLS certificate valid for 146 days
Certificate for dhgate.com expires on 2026-10-23.
Certificate issued by DigiCert Global G3 TLS ECC SHA384 2020 CA1
The certificate for dhgate.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for dhgate.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for dhgate.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for dhgate.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on dhgate.com.
Domain valid for 113 days
Domain dhgate.com expires on 2026-09-21.
Domain transfer and delete locks enabled
Domain dhgate.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for dhgate.com do not match known disposable email provider patterns.
Domain is 7921 days old
Domain dhgate.com was registered 2004-09-21.
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 (mx1.feishu.cn) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 including Forward Secrecy.
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.
WHOIS registration data
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd. | Created: 2004-09-21 | Expires: 2026-09-21 | Updated: 2024-08-20
WHOIS privacy protection not detected
Domain dhgate.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: dgate.com (has MX!), dhgte.com (has MX!), dhgae.com (has MX!), dhgat.com (has MX!), dhagte.com (has MX!)
26 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 26. 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 missing
⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
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: mx2.feishu.cn
PTR record proves mail server legitimacy
MX: mx2.feishu.cn
Mail server at 101.126.58.225
→
PTR Record
No PTR record
⚠️ Mail server mx2.feishu.cn (101.126.58.225) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx3.feishu.cn
PTR record proves mail server legitimacy
MX: mx3.feishu.cn
Mail server at 101.126.58.225
→
PTR Record
No PTR record
⚠️ Mail server mx3.feishu.cn (101.126.58.225) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx1.feishu.cn
PTR record proves mail server legitimacy
MX: mx1.feishu.cn
Mail server at 52.220.106.220
→
PTR Record
Reverse DNS: ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com
Mail Server Reputation: mx2.feishu.cn
RBL check ensures server is not blacklisted
MX: mx2.feishu.cn
Mail server at 101.126.58.225
→
RBL Status
Not blacklisted
Mail Server Reputation: mx3.feishu.cn
RBL check ensures server is not blacklisted
MX: mx3.feishu.cn
Mail server at 101.126.58.225
→
RBL Status
Not blacklisted
Mail Server Reputation: mx1.feishu.cn
RBL check ensures server is not blacklisted
MX: mx1.feishu.cn
Mail server at 52.220.106.220
→
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 failure reporting configured
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/dhgate.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan dhgate.com Again