Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
assembly.com scored 98/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, Known Breaches, HSTS Header 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 assembly.com compares
Grade distribution across 2378 companies we've scanned. assembly.com scores better than 97% 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
assembly.com — Grade A+ (98/100)
2378 companies scanned
Security checks
Each check inspects a different part of assembly.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 4 nameservers configured (ns-27.awsdns-03.com., ns-851.awsdns-42.net., ns-1295.awsdns-33.org., ns-1618.awsdns-10.co.uk.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=63072000. Missing includeSubDomains. Missing preload directive.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
CVE Exposure
Detected technologies: Vercel, Next.js. (Vercel 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, 68 days remaining; Issued by Let's Encrypt.
Recommended actions
1 item
Steps to improve assembly.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for assembly.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 assembly.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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
SPF Record
Present
v=spf1 include:_spf.google.com include:amazonses.com ~all
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 68 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-27.awsdns-03.com., ns-851.awsdns-42.net., ns-1295.awsdns-33.org., ns-1618.awsdns-10.co.uk.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.