Overview
Findings
Actions
Details
Related
B
85 / 100

sortingrobotics.com

Security report · Scanned February 18, 2026

Checks
8
Passed
6
Warnings
1
Critical
1
AI-Generated Summary
What this means

sortingrobotics.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.

Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, DNS Configuration all passed.

2 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 sortingrobotics.com compares

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

78th 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
sortingrobotics.com — Grade B (85/100) 2378 companies scanned
Security checks

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

Security Headers
Only 2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Problem
HSTS Header
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-d4.googledomains.com., ns-cloud-d3.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
CVE Exposure
Detected technologies: Squarespace. No version information exposed — CVE matching not possible (this is good practice).
Healthy
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2). Issues: DMARC has no aggregate report URI (rua).
Healthy
Certificate Hygiene
Strengths: Certificate valid, 62 days remaining; Issued by Let's Encrypt.
Healthy
Recommended actions
2 items

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

1
Add missing security headers (CSP, Referrer-Policy, Permissions-Policy)
Impact: 1–2 Hours
HIGH
3 of 5 recommended security headers are missing on sortingrobotics.com: CSP, 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 Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://sortingrobotics.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
2
Increase HSTS max-age duration
Impact: < 30 Minutes
MEDIUM
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://sortingrobotics.com | grep -i strict
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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2). Issues: DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 include:_spf.google.com include:446262632.spf04.hubspotemail.net ~all
Security Headers
2/5 present
Missing: CSP, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Valid
Strengths: Certificate valid, 62 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-d4.googledomains.com., ns-cloud-d3.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.