Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
pools.events scored 75/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header. Positive signals: Known Breaches, Security Headers, TLS Configuration all passed.
4 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 pools.events compares
Grade distribution across 2378 companies we've scanned. pools.events scores better than 55% 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
pools.events — Grade C (75/100)
2378 companies scanned
Security checks
Each check inspects a different part of pools.events's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
DNS Configuration
Strengths: 2 nameservers configured (demi.ns.cloudflare.com., benedict.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
Certificate Hygiene
Strengths: Certificate valid, 88 days remaining; Issued by Google Trust Services. 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.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
CVE Exposure
Detected technologies: cloudflare, Proxy/CDN. (cloudflare, Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Recommended actions
4 items
Steps to improve pools.events's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for pools.events but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.pools.events
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on pools.events. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://pools.events | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for pools.events 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 .events TLD
4
Verify: dig +dnssec pools.events
4
Review certificate configuration
Certificate issues found for pools.events: 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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:_spf.google.com ~all
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Issues
Strengths: Certificate valid, 88 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (demi.ns.cloudflare.com., benedict.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.