Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
temu.com scored 98/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Cookie Security. Positive signals: TLS Configuration, TLS Protocol Support, Known Breaches all passed.
1 action item identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How temu.com compares
Grade distribution across 2619 companies we've scanned. temu.com scores better than 97% of them.
87
A+
26
A
190
A-
198
B+
75
B
362
B-
132
C+
115
C
334
C-
121
D+
95
D
256
D-
628
F
temu.com — Grade A+ (98/100)
2619 companies scanned
Security checks
Each check inspects a different part of temu.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
Strengths: 3 cookie(s) analyzed; All cookies have Secure flag. Issues: 3/3 cookie(s) missing HttpOnly flag (region, language, currency); 3/3 cookie(s) missing SameSite attribute (region, language, currency).
MX Records & Mail Provider
Strengths: Mail handled by mxmail-in.temu.com; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 4 nameservers configured (ns4-35.azure-dns.info., ns1-35.azure-dns.com., ns2-35.azure-dns.net., ns3-35.azure-dns.org.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
HSTS Header
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 104 days remaining; Issued by GoDaddy.com, Inc.; 163 certificates logged in CT; Certificates from 5 CAs: "DigiCert, "GoDaddy.com, GlobalSign nv-sa. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
1 item
Steps to improve temu.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for temu.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec temu.com
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 include:_spf.google.com include:_spf_mail.temu.com include:_spf_mail_eu.temu.com include:_spf
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 104 days remaining; Issued by GoDaddy.com, Inc.; 163 certificates logged in CT; Certificates from 5 CAs: "DigiCert, "GoDaddy.com, GlobalSign nv-sa. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns4-35.azure-dns.info., ns1-35.azure-dns.com., ns2-35.azure-dns.net., ns3-35.azure-dns.org.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.