Overview
Findings
Actions
Details
Related
B
85 / 100

backerkit.com

Security report · Scanned February 18, 2026

Checks
8
Passed
5
Warnings
3
Critical
0
AI-Generated Summary
What this means

backerkit.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.

Positive signals: DNS Configuration, Known Breaches, TLS Configuration all passed.

3 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 backerkit.com compares

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

78th 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
backerkit.com — Grade B (85/100) 2378 companies scanned
Security checks

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

HSTS Header
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
Needs work
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
Needs work
Certificate Hygiene
Strengths: Certificate valid, 67 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
Needs work
DNS Configuration
Strengths: 2 nameservers configured (clint.ns.cloudflare.com., emma.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, k1).
Healthy
CVE Exposure
Detected technologies: cloudflare, Phusion Passenger(R) Enterprise 6.1.2, Proxy/CDN. (cloudflare, Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Healthy
Recommended actions
3 items

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

1
Increase HSTS max-age duration
Impact: < 30 Minutes
MEDIUM
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://backerkit.com | grep -i strict
2
Add optional security headers (CSP, Permissions-Policy)
Impact: < 1 Hour
LOW
backerkit.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://backerkit.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for backerkit.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 soft-fail (~all); DKIM configured (selectors: google, k1).
SPF Record
Present
v=spf1 include:_spf.google.com include:mailgun.org include:servers.mcsv.net include:mktomail.com inc
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 67 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (clint.ns.cloudflare.com., emma.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.