Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
duffel.com scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, TLS Configuration, 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 duffel.com compares
Grade distribution across 2378 companies we've scanned. duffel.com scores better than 96% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
duffel.com — Grade A (95/100)
2378 companies scanned
Security checks
Each check inspects a different part of duffel.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
DNS Configuration
Strengths: 2 nameservers configured (lakas.ns.cloudflare.com., jocelyn.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, zendesk1, zendesk2).
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
CVE Exposure
Detected technologies: cloudflare, Next.js, Proxy/CDN. (cloudflare, Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 74 days remaining; Issued by Google Trust Services.
Recommended actions
1 item
Steps to improve duffel.com's security grade, ranked by impact.
1
Add optional security headers (CSP, Permissions-Policy)
duffel.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://duffel.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-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); DKIM configured (selectors: google, zendesk1, zendesk2).
SPF Record
Present
v=spf1 include:mail.zendesk.com include:_spf.google.com include:emsd1.com -all
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 74 days remaining; Issued by Google Trust Services.
DNSSEC
Enabled
Strengths: 2 nameservers configured (lakas.ns.cloudflare.com., jocelyn.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.