Identity
62
C
aliexpress.com
Posture Score: 72/100
Scanned May 27, 2026 at 6:41 AM UTC
Attack Surface
87
Reputation
68
Identity Findings
MX hostname resolves via CNAME: mx2.mail.aliyun.com
MX records should not point to a CNAME (RFC 2181). This can cause delivery failures.
💡 Point the MX record directly to an A/AAAA record, not a CNAME.
FCrDNS failure: no PTR for 106.11.232.89 (mx2.mail.aliyun.com)
The IP 106.11.232.89 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 PTR record for MX IP: 106.11.232.89
The IP 106.11.232.89 (for mx2.mail.aliyun.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.aliexpress.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@aliexpress.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.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (105 bytes)
SPF record is within safe DNS packet size limits.
DKIM records are valid
DKIM records found and validated for selectors: s1
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.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
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).
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
VMC URL is accessible
The BIMI VMC authority URL is reachable and returns a valid response.
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.
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.
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.
Open mail ports on mx2.mail.aliyun.com
Detected open mail-related ports: 25
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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2018051019, Refresh: 3600s, Retry: 1200s, Expire: 86400s, Min TTL: 360s
Attack Surface Findings
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.aliexpress.com/autodiscover/autodiscover.xml returns configuration data without requiring authentication. This exposes email server details to unauthenticated users.
💡 Configure the Autodiscover endpoint to require authentication before returning configuration data.
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.
30 subdomain(s) discovered for aliexpress.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 aliexpress.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.aliexpress.com, resolving to 47.89.80.142. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.aliexpress.com is publicly accessible.
Reputation Findings
Listed on dnsbl.spfbl.net
106.11.232.89 (mx2.mail.aliyun.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.
SMTP banner mismatch: mx1.aliyun-inc.com
The SMTP banner identifies as 'mx1.aliyun-inc.com' but the MX hostname is 'mx2.mail.aliyun.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mx2.mail.aliyun.com).
HSTS effectively disabled on aliexpress.com (max-age=0)
The HSTS header has max-age=0, which instructs browsers to forget the HSTS policy. This provides no transport security enforcement.
💡 Set max-age to at least 31536000 (1 year) to enforce HTTPS.
Wildcard MX records detected
Domain aliexpress.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 but missing preload directive on webmail.aliexpress.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://aliexpress.com/.well-known/security.txt.
TLS certificate valid for 190 days
Certificate for aliexpress.com expires on 2026-12-03.
Certificate issued by GlobalSign GCC R3 OV TLS CA 2024
The certificate for aliexpress.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for aliexpress.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for aliexpress.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for aliexpress.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on aliexpress.com.
Domain valid for 1420 days
Domain aliexpress.com expires on 2030-04-16.
Domain transfer and delete locks enabled
Domain aliexpress.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for aliexpress.com do not match known disposable email provider patterns.
Domain is 7345 days old
Domain aliexpress.com was registered 2006-04-16.
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 (mx2.mail.aliyun.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 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: Alibaba Cloud Computing (Beijing) Co., Ltd. | Created: 2006-04-16 | Expires: 2030-04-16 | Updated: 2026-03-19
WHOIS privacy protection not detected
Domain aliexpress.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: liexpress.com (has MX!), aliexress.com (has MX!), aliexpess.com (has MX!), ailexpress.com (has MX!), aleixpress.com (has MX!)
28 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 28. 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: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy: reject
Mail Server Identity: mx2.mail.aliyun.com
PTR record proves mail server legitimacy
MX: mx2.mail.aliyun.com
Mail server at mx2.mail.aliyun.com.gds.alibabadns.com
→
PTR Record
No PTR record
⚠️ Mail server mx2.mail.aliyun.com (mx2.mail.aliyun.com.gds.alibabadns.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mx2.mail.aliyun.com
RBL check ensures server is not blacklisted
MX: mx2.mail.aliyun.com
Mail server at mx2.mail.aliyun.com.gds.alibabadns.com
→
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:
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
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/aliexpress.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan aliexpress.com Again