Overview
Findings
Actions
Details
Related
D
65 / 100

doublerobotics.com

Security report · Scanned February 18, 2026

Checks
8
Passed
4
Warnings
2
Critical
2
AI-Generated Summary
What this means

doublerobotics.com scored 65/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: Security Headers, CVE Exposure. Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.

4 action items 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 doublerobotics.com compares

Grade distribution across 2378 companies we've scanned. doublerobotics.com scores better than 34% of them.

34th percentile
0 Percentile rank 100
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
doublerobotics.com — Grade D (65/100) 2378 companies scanned
Security checks

Each check inspects a different part of doublerobotics.com's public security setup. Green means healthy, yellow needs attention, red is a problem.

Security Headers
Only 2/5 security headers present. Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Problem
CVE Exposure
Detected technologies: Apache/2.4.52, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). 3 critical-severity CVE(s) found (CVSS >= 9.0): CVE-2022-22720, CVE-2022-22721, CVE-2022-23943. Immediate patching recommended.
Problem
DNS Configuration
Strengths: 4 nameservers configured (ns-132.awsdns-16.com., ns-1977.awsdns-55.co.uk., ns-800.awsdns-36.net., ns-1087.awsdns-07.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Needs work
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Healthy
Certificate Hygiene
Strengths: Certificate valid, 68 days remaining; Issued by Let's Encrypt.
Healthy
Recommended actions
4 items

Steps to improve doublerobotics.com's security grade, ranked by impact.

1
Strengthen email authentication configuration
Impact: 2–4 Hours
HIGH
Email authentication is partially configured for doublerobotics.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.doublerobotics.com
2
Add missing security headers (X-Frame-Options, Referrer-Policy, Permissions-Policy)
Impact: 1–2 Hours
HIGH
3 of 5 recommended security headers are missing on doublerobotics.com: X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://doublerobotics.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Patch 3 critical CVEs
Impact: 1–2 Days
HIGH
Externally visible software on doublerobotics.com has 3 critical CVEs (CVSS >= 9.0). Update the affected software to the latest patched version.
Compliance impact
NIST 800-53SI-2
Flaw remediation
PCI-DSS 4.0Req 6.3.3
Critical patches within 1 month
How to fix this
1
Review CVEs: CVE-2022-22720, CVE-2022-22721, CVE-2022-23943
2
Update affected software to latest patched versions
3
Verify patches applied: re-scan after update
4
Consider hiding server version headers to reduce future exposure
4
Enable DNSSEC on your domain
Impact: 1–3 Days (Depends On Registrar)
MEDIUM
Without DNSSEC, DNS responses for doublerobotics.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 doublerobotics.com
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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:_spf.google.com include:authsmtp.com include:_spf.salesforce.com ~all
Security Headers
2/5 present
Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 68 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-132.awsdns-16.com., ns-1977.awsdns-55.co.uk., ns-800.awsdns-36.net., ns-1087.awsdns-07.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.