Overview
Findings
Actions
Details
Related
LynxRadar → Directory → armory.io
F
55 / 100

armory.io

Security report · Scanned February 18, 2026

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

armory.io scored 55/100 and does not meet the minimum security posture threshold. The most critical issue is: Upgrade TLS — deprecated protocol in use. This must be addressed before the vendor can be approved for procurement or data processing activities.

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

2 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

How armory.io compares

Grade distribution across 2378 companies we've scanned. armory.io 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
armory.io — Grade F (55/100) 2378 companies scanned
Security checks

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

TLS Configuration
TLS certificate verification failed on armory.io: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'armory.io'. (_ssl.c:1081)
Problem
Certificate Hygiene
Issues: Could not retrieve certificate details.
Needs work
HSTS Header
Could not fetch https://armory.io — connection failed or timed out.
Skipped
Security Headers
Could not fetch https://armory.io — 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-b1.googledomains.com., ns-cloud-b4.googledomains.com., ns-cloud-b3.googledomains.com., ns-cloud-b2.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, s1, s2, k1, mandrill).
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
2 items

Steps to improve armory.io's security grade, ranked by impact.

1
Upgrade TLS — deprecated protocol in use
Impact: 1–2 Hours
CRITICAL
armory.io is using unknown, which is deprecated and has known vulnerabilities. This is a compliance failure under PCI-DSS, HIPAA, and NIST guidelines. Immediate upgrade to TLS 1.2 minimum (TLS 1.3 preferred) is required.
Compliance impact
PCI-DSS 4.0Req 4.2.1
Strong cryptography for transmission
NIST 800-52r2§3.4
TLS 1.0/1.1 must not be used
HIPAA§164.312(e)
Transmission security
How to fix this
1
Disable TLS 1.0 and 1.1 in your web server configuration
2
Enable TLS 1.2 and 1.3: ssl_protocols TLSv1.2 TLSv1.3
3
Remove weak ciphers: ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:...'
4
Verify: openssl s_client -connect armory.io:443 -tls1_2
2
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for armory.io: . 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
TLS certificate verification failed on armory.io: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'armory.io'. (_ssl.c:1081)
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, k1, mandrill).
SPF Record
Present
v=spf1 include:_spf.google.com ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://armory.io — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-b1.googledomains.com., ns-cloud-b4.googledomains.com., ns-cloud-b3.googledomains.com., ns-cloud-b2.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.