Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
humi.ca scored 72/100, meeting baseline requirements but with 1 finding that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers, CVE Exposure. Positive signals: Known Breaches, TLS Configuration, DMARC / Email Security 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 humi.ca compares
Grade distribution across 2378 companies we've scanned. humi.ca scores better than 47% 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
humi.ca — Grade C- (72/100)
2378 companies scanned
Security checks
Each check inspects a different part of humi.ca's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 2/5 security headers present. Missing: CSP, X-Frame-Options, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
CVE Exposure
Detected technologies: nginx, PHP/8.1.32, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). 1 critical-severity CVE(s) found (CVSS >= 9.0): CVE-2025-1861. Immediate patching recommended.
DNS Configuration
Strengths: 4 nameservers configured (ns-1780.awsdns-30.co.uk., ns-271.awsdns-33.com., ns-1017.awsdns-63.net., ns-1047.awsdns-02.org.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
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.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, k1).
Certificate Hygiene
Strengths: Certificate valid, 38 days remaining; Issued by Let's Encrypt.
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. preload present.
Recommended actions
3 items
Steps to improve humi.ca's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Frame-Options, Permissions-Policy)
3 of 5 recommended security headers are missing on humi.ca: CSP, X-Frame-Options, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://humi.ca | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Patch 1 critical CVE
Externally visible software on humi.ca has 1 critical CVE (CVSS >= 9.0). Update the affected software to the latest patched version.
Compliance impact
NIST 800-53SI-2
Flaw remediation
PCI-DSS 4.0Req 6.3.3
Critical patches within 1 month
How to fix this
1
Review CVEs: CVE-2025-1861
2
Update affected software to latest patched versions
3
Verify patches applied: re-scan after update
4
Consider hiding server version headers to reduce future exposure
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for humi.ca 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 .ca TLD
4
Verify: dig +dnssec humi.ca
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, s1, s2, k1).
SPF Record
Present
v=spf1 include:2445023.spf08.hubspotemail.net include:mailgun.org include:_spf.google.com include:se
Security Headers
2/5 present
Missing: CSP, X-Frame-Options, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. preload present.
SSL Certificate
Valid
Strengths: Certificate valid, 38 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1780.awsdns-30.co.uk., ns-271.awsdns-33.com., ns-1017.awsdns-63.net., ns-1047.awsdns-02.org.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.