Overview
Findings
Actions
Details
Related
LynxRadar → Directory → dashblock.com
F
55 / 100

dashblock.com

Security report · Scanned February 18, 2026

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

dashblock.com scored 55/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.

Positive signals: Known Breaches, DNS Configuration, DMARC / Email Security 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 dashblock.com compares

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

18th 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
dashblock.com — Grade F (55/100) 2378 companies scanned
Security checks

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

Certificate Hygiene
Issues: Could not retrieve certificate details.
Needs work
TLS Configuration
Could not complete TLS handshake with dashblock.com:443 — [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)
Skipped
HSTS Header
Could not fetch https://dashblock.com — connection failed or timed out.
Skipped
Security Headers
Could not fetch https://dashblock.com — connection failed or timed out.
Skipped
Known Breaches
No known breaches found in public disclosure databases.
Healthy
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-e4.googledomains.com., ns-cloud-e2.googledomains.com., ns-cloud-e3.googledomains.com., ns-cloud-e1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
Healthy
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Healthy
Recommended actions
1 item

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

1
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for dashblock.com: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
At a glance

Key data points from the scan.

TLS Version
Issues detected
Could not complete TLS handshake with dashblock.com:443 — [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)
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.mandrillapp.com include:_spf.google.com include:6283962.spf05.hubspotemail.net ~a
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://dashblock.com — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-e4.googledomains.com., ns-cloud-e2.googledomains.com., ns-cloud-e3.googledomains.com., ns-cloud-e1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.