Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
ashbyhq.com scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, TLS Configuration, 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 ashbyhq.com compares
Grade distribution across 2378 companies we've scanned. ashbyhq.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
ashbyhq.com — Grade A (95/100)
2378 companies scanned
Security checks
Each check inspects a different part of ashbyhq.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Certificate Hygiene
Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (jillian.ns.cloudflare.com., kip.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2).
CVE Exposure
Detected technologies: Netlify, Next.js. (Netlify detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
Security Headers
4/5 security headers present. Missing: Referrer-Policy.
Recommended actions
1 item
Steps to improve ashbyhq.com's security grade, ranked by impact.
1
Review certificate configuration
Certificate issues found for ashbyhq.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2).
SPF Record
Present
v=spf1 include:_spf.google.com include:stspg-customer.com include:4990969.spf05.hubspotemail.net exi
Security Headers
4/5 present
Missing: Referrer-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (jillian.ns.cloudflare.com., kip.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.