Does dji.com have DMARC protection against email spoofing?

Partly. dji.com publishes DMARC with p=quarantine at 100% coverage — better than nothing, but forged messages can still reach inboxes that do not enforce the policy.

How is dji.com's C security grade calculated?

CyberTrust scores dji.com passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; email spoofing defences (SPF/DKIM/DMARC) 84/100; DNS hygiene 84/100; TLS encryption and certificates 26/100; HTTP security headers 12/100 — and combines them by weight into the overall score of 71/100, which maps to grade C.

How many subdomains does dji.com expose?

This scan observed 50 publicly resolvable subdomain(s) for dji.com. Verified owners get the full list, with each host's open ports and running services.

Public security report

dji.com security rating

71/100

A means lowest risk and F means highest, like a school report card. How the score is calculated →

Scanned 2026-10-30 · 14 issue(s) found · 14 checks passed

Re-scan dji.com now

What this scan found

CyberTrust assessed dji.com passively — using only information that is publicly visible on the internet: DNS records, certificates, response headers and reachable services. The result is 71/100, grade C, where A means lowest risk and F means highest, like a school report card.

Email spoofing is only partly blocked: DMARC is published with p=quarantine at 100% coverage, so forged mail can still reach inboxes that do not enforce the policy.

Strongest area: external attack surface (100/100). Weakest area: HTTP security headers (12/100).

14 issue(s) need attention (3 medium, 11 low), while 14 checks passed.

Infrastructure observed: DNS is served by route53, traffic is fronted by cloudfront, the web server identifies as openresty.

50 subdomain(s) of dji.com resolve publicly.

Score by category

Area	Score	Grade	Issues
DNS hygiene	84	B	2
email spoofing defences (SPF/DKIM/DMARC)	84	B	2
external attack surface	100	A	0
IP threat intelligence	—	—	0
reputation and credential exposure	100	A	0
TLS encryption and certificates	26	F	3
HTTP security headers	12	F	7

Issues found (14)

mediumOutdated TLS versions enabled (TLSv1.1)

Versions TLSv1.1 are formally deprecated, fail PCI DSS requirements and are no longer supported by modern browsers; they also enable downgrade attacks and fail compliance audits.

6 asset(s) affected · worth +6 points · how to read an SSL/TLS certificate check →

mediumDES/3DES cipher accepted

64-bit block ciphers are vulnerable to SWEET32 after enough data on one connection, and 3DES is no longer accepted by compliance standards.

1 asset(s) affected · worth +3 points · how to read an SSL/TLS certificate check →

mediumHSTS not enabled

Without it, an attacker can strip SSL on the first HTTP request and keep the user on plaintext (SSL stripping), a common attack on public Wi-Fi.

1 asset(s) affected · worth +3 points · how to set HSTS, CSP and other security headers →

lowNo OCSP stapling

The server does not staple the certificate revocation status. Every revocation check becomes an extra round trip to the CA, which slows the first visit and, if the CA endpoint is unreachable or the visitor's network blocks it, leaves the browser without a usable revocation status.

4 asset(s) affected · worth +2 points · check a certificate with the free SSL tool →

lowCookies without Secure/HttpOnly (lang, region)

Missing Secure lets cookies travel in plaintext; missing HttpOnly lets injected scripts steal sessions; missing SameSite enables CSRF. Affected: lang, region.

4 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowNo Content Security Policy

Without it, any injected script runs: session theft, fake payment forms, or card-skimming scripts on compromised pages. CSP limits the damage even when something else fails.

4 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowContent Security Policy is weak (no script-src/default-src; object-src not restricted)

The policy is too permissive (no script-src/default-src; object-src not restricted), so injected scripts still run while giving a false sense of security.

4 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowWeak DKIM key: 1024-bit RSA (selector k1)

At 1024 bits (selector k1) the key is considered weak; 1024-bit keys can be broken cheaply, letting attackers sign mail that passes DKIM.

1 asset(s) affected · worth +2 points · look up DKIM keys with the free DKIM tool →

lowNo MTA-STS policy

Without it an attacker on the network path can force a downgrade to plaintext and read or modify mail such as contracts and payment details.

1 asset(s) affected · worth +2 points · how to stop email spoofing with SPF, DKIM and DMARC →

lowHSTS preload not enabled

Even with HSTS on, the very first visit is still exposed to SSL-stripping: the header only takes effect after one successful HTTPS visit. Browsers ship a preload list (Chromium's list is used by Chrome, Edge, Safari and Firefox) so the first connection goes straight to HTTPS.

2 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowNo CAA record

Without it any CA may issue certificates for your domain, enabling a lookalike site with a valid padlock.

1 asset(s) affected · worth +1 points · see who can issue certificates with the free CAA tool →

lowDNSSEC not enabled

Without it, attackers can poison caches or forge answers and send visitors to a lookalike server that harvests credentials.

1 asset(s) affected · worth +1 points · what DNSSEC prevents and how to enable it →

lowX-Content-Type-Options missing

Without it a file uploaded as an image can be executed as HTML/JavaScript on your domain, stealing same-site cookies and sessions.

1 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowNo clickjacking protection

Without it, attackers overlay a transparent frame of your page and trick users into clicking real actions such as transfers or password changes (clickjacking).

1 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

Checks passed

Mail exchangers configured
SPF record is valid
DMARC policy is enforced
Name servers are redundant
HSTS enabled
Clickjacking protection enabled
MIME sniffing disabled
No API keys found in front-end bundles
No weak cipher suites accepted
Certificate is valid and trusted
Only modern TLS versions are enabled
No risky services found exposed
No shadow-AI services exposed
No mail-server IP on spam blocklists

What we detected

dns provider: route53
cdn: cloudfront
web server: openresty
subdomain count: 50

What could not be fully checked

DMARC quarantines spoofed mail
p=quarantine sends failing mail to spam. p=reject blocks it outright and is the strongest protection.
No BIMI record
BIMI shows your logo next to authenticated mail in supporting inboxes (requires an enforcing DMARC policy). It is a trust signal rather than a security control, so it does not affect your score.
No TLS-RPT record
TLS-RPT sends you reports when other servers fail to deliver mail to you securely. Recommended alongside MTA-STS.
No Permissions-Policy 8 host(s)
Permissions-Policy disables powerful browser features (camera, microphone, geolocation) you do not use.
No security.txt 2 host(s)
security.txt (RFC 9116) tells security researchers how to report vulnerabilities to you instead of posting them publicly.
No Referrer-Policy 4 host(s)
Browsers default to strict-origin-when-cross-origin today; setting it explicitly is good hygiene.
Website redirects to an external platform
Headers on third-party hosted pages are controlled by that platform and are not scored.
Website returned an error page — partly unassessed
The page returned HTTP 403 (often a firewall challenge for automated clients), so most header and content checks could not run. HSTS was still assessed where the response is reliable, but this category is only partially evaluated and its score should be read as incomplete.
RSA key exchange still accepted 8 host(s)
Static RSA key exchange is kept for old clients. It lacks forward secrecy but is not scored when ECDHE is available.
TLS 1.3 not enabled 2 host(s)
TLS 1.3 is faster and removes legacy cryptography. Recommended, but not required.

Frequently asked questions about dji.com security

Does dji.com have DMARC protection against email spoofing?: Partly. dji.com publishes DMARC with p=quarantine at 100% coverage — better than nothing, but forged messages can still reach inboxes that do not enforce the policy.
How is dji.com's C security grade calculated?: CyberTrust scores dji.com passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; email spoofing defences (SPF/DKIM/DMARC) 84/100; DNS hygiene 84/100; TLS encryption and certificates 26/100; HTTP security headers 12/100 — and combines them by weight into the overall score of 71/100, which maps to grade C.
What is the most serious issue found on dji.com?: Outdated TLS versions enabled (TLSv1.1) (severity medium). Versions TLSv1.1 are formally deprecated, fail PCI DSS requirements and are no longer supported by modern browsers; they also enable downgrade attacks and fail compliance audits. Fixing it is worth about +6 points.
How many subdomains does dji.com expose?: This scan observed 50 publicly resolvable subdomain(s) for dji.com. Verified owners get the full list, with each host's open ports and running services.

What a verified owner of dji.com sees

Everything above is what anyone can observe from the internet. Domain owners who verify ownership additionally get the full asset inventory — every subdomain with its open ports and running services — look-alike and typosquatting domains registered against the brand, credential-exposure monitoring, and copy-paste fixes for each finding.

Verify ownership of dji.com (free) → Open the live interactive report →