Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
rainforestqa.com scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, Known Breaches, TLS Configuration all passed.
2 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 rainforestqa.com compares
Grade distribution across 2378 companies we've scanned. rainforestqa.com scores better than 89% 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
rainforestqa.com — Grade A- (90/100)
2378 companies scanned
Security checks
Each check inspects a different part of rainforestqa.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
DNS Configuration
Strengths: 2 nameservers configured (dora.ns.cloudflare.com., ed.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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 quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, zendesk1, zendesk2, smtpapi).
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 62 days remaining; Issued by Google Trust Services.
Recommended actions
2 items
Steps to improve rainforestqa.com's security grade, ranked by impact.
1
Increase HSTS max-age duration
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://rainforestqa.com | grep -i strict
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (Referrer-Policy, Permissions-Policy)
rainforestqa.com has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://rainforestqa.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, zendesk1, zendesk2, smtpapi).
SPF Record
Present
v=spf1 mx include:_spf.google.com include:spf.mail.intercom.io include:22286279.spf07.hubspotemail.n
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Valid
Strengths: Certificate valid, 62 days remaining; Issued by Google Trust Services.
DNSSEC
Enabled
Strengths: 2 nameservers configured (dora.ns.cloudflare.com., ed.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.