Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
producthunt.com scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, TLS Configuration, Known Breaches 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 producthunt.com compares
Grade distribution across 2378 companies we've scanned. producthunt.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
producthunt.com — Grade A- (90/100)
2378 companies scanned
Security checks
Each check inspects a different part of producthunt.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
HSTS present but max-age is low (2592000s). Recommended minimum: 15768000 (6 months).
Certificate Hygiene
Strengths: Certificate valid, 52 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (tia.ns.cloudflare.com., alexis.ns.cloudflare.com.); 7 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
Security Headers
4/5 security headers present. Missing: CSP.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1).
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.
Recommended actions
2 items
Steps to improve producthunt.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://producthunt.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
Review certificate configuration
Certificate issues found for producthunt.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
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, k1).
SPF Record
Present
v=spf1 include:spf.mail.intercom.io include:spf.mailjet.com include:_spf.mailgun.org include:_spf.eu
Security Headers
4/5 present
Missing: CSP
HSTS
Not enabled
HSTS present but max-age is low (2592000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 52 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (tia.ns.cloudflare.com., alexis.ns.cloudflare.com.); 7 MX records present; DNSSEC enabled; Zone transfers properly restricted.