Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
abacus.com scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, DMARC / Email Security, HSTS Header 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 abacus.com compares
Grade distribution across 2378 companies we've scanned. abacus.com scores better than 81% 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
abacus.com — Grade B+ (88/100)
2378 companies scanned
Security checks
Each check inspects a different part of abacus.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 4 nameservers configured (ns-171.awsdns-21.com., ns-1957.awsdns-52.co.uk., ns-570.awsdns-07.net., ns-1331.awsdns-38.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
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: k1, zendesk1, zendesk2).
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
CVE Exposure
Detected technologies: envoy. (envoy detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 335 days remaining; Issued by Amazon.
Recommended actions
2 items
Steps to improve abacus.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for abacus.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 abacus.com
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Upgrade to TLS 1.3
abacus.com negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect abacus.com:443 -tls1_3
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: k1, zendesk1, zendesk2).
SPF Record
Present
v=spf1 include:_spf.google.com include:mailgun.org include:servers.mcsv.net include:mktomail.com inc
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 335 days remaining; Issued by Amazon.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-171.awsdns-21.com., ns-1957.awsdns-52.co.uk., ns-570.awsdns-07.net., ns-1331.awsdns-38.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.