Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
ironcladapp.com scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, DNS Configuration, TLS Configuration 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 ironcladapp.com compares
Grade distribution across 2378 companies we've scanned. ironcladapp.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
ironcladapp.com — Grade A (95/100)
2378 companies scanned
Security checks
Each check inspects a different part of ironcladapp.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Certificate Hygiene
Strengths: Certificate valid, 61 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-e4.googledomains.com., ns-cloud-e3.googledomains.com., ns-cloud-e2.googledomains.com., ns-cloud-e1.googledomains.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.
HSTS Header
HSTS enabled: max-age=63072000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
CVE Exposure
Detected technologies: WP Engine, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, mandrill, zendesk1, zendesk2).
Recommended actions
1 item
Steps to improve ironcladapp.com's security grade, ranked by impact.
1
Review certificate configuration
Certificate issues found for ironcladapp.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, mandrill, zendesk1, zendesk2).
SPF Record
Present
v=spf1 a include:_spf.google.com include:mail.zendesk.com include:spf.mandrillapp.com include:mktoma
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 61 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-e4.googledomains.com., ns-cloud-e3.googledomains.com., ns-cloud-e2.googledomains.com., ns-cloud-e1.googledomains.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.