Identity
0
F
tradplusad.com
Posture Score: 47/100
Scanned May 28, 2026 at 3:17 AM UTC
Attack Surface
76
Reputation
65
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.tradplusad.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@tradplusad.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 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.
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.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
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.tradplusad.com
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: 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 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.
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.tradplusad.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.tradplusad.com
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@tradplusad.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 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.
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.
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 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.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
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 mx1.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
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2025121107, Refresh: 3600s, Retry: 1200s, Expire: 86400s, Min TTL: 600s
Attack Surface Findings
Non-routable IPv4 in public DNS: dev.tradplusad.com → 10.12.1.22
The subdomain dev.tradplusad.com resolves to non-routable IP 10.12.1.22, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: test.tradplusad.com → 10.12.1.21
The subdomain test.tradplusad.com resolves to non-routable IP 10.12.1.21, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
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 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.
8 subdomain(s) discovered for tradplusad.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 tradplusad.com and its subdomains. Each certificate reveals subdomain names.
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.
Missing domain locks: clientTransferProhibited, clientDeleteProhibited
Domain tradplusad.com is missing protective locks: clientTransferProhibited, clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
SMTP banner mismatch: n126-036-051
The SMTP banner identifies as 'n126-036-051' 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 tradplusad.com
The Strict-Transport-Security header is not set on https://tradplusad.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://tradplusad.com/.well-known/security.txt.
TLS certificate valid for 221 days
Certificate for tradplusad.com expires on 2027-01-04.
Certificate issued by Encryption Everywhere DV TLS CA - G2
The certificate for tradplusad.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for tradplusad.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for tradplusad.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for tradplusad.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on tradplusad.com.
Domain valid for 190 days
Domain tradplusad.com expires on 2026-12-04.
No disposable email provider MX records
MX records for tradplusad.com do not match known disposable email provider patterns.
Domain is 2000 days old
Domain tradplusad.com was registered 2020-12-04.
No wildcard MX records
No wildcard MX records detected for tradplusad.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 (mx1.feishu.cn) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 including Forward Secrecy.
No registered typosquat domains detected
None of the common typosquat mutations of this domain appear to be registered by third parties.
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.tradplusad.com
HTTPS request to https://webmail.tradplusad.com failed or timed out.
WHOIS registration data
Registrar: Alibaba Cloud Computing (Beijing) Co., Ltd. | Created: 2020-12-04 | Expires: 2026-12-04 | Updated: 2025-03-20
WHOIS privacy protection not detected
Domain tradplusad.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).
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: 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 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 52.220.106.220
→
PTR Record
Reverse DNS: ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com
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
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 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
Mode: enforce
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/tradplusad.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan tradplusad.com Again