Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
worldpossible.org scored 75/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Cookie Security, DMARC / Email Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.
3 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How worldpossible.org compares
Grade distribution across 2449 companies we've scanned. worldpossible.org scores better than 55% of them.
75
A+
24
A
181
A-
187
B+
71
B
342
B-
118
C+
113
C
309
C-
114
D+
93
D
226
D-
596
F
worldpossible.org — Grade C (75/100)
2449 companies scanned
Security checks
Each check inspects a different part of worldpossible.org's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
Strengths: 7 cookie(s) analyzed. Issues: 4/7 cookie(s) missing Secure flag (localization, cart_currency, _shopify_y...); 4/7 cookie(s) missing HttpOnly flag (localization, cart_currency, _shopify_y...); 2/7 cookie(s) missing SameSite attribute (localization, cart_currency).
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
HSTS Header
HSTS configured with max-age=7889238s (91 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-d1.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d4.googledomains.com., ns-cloud-d3.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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, 85 days remaining; Issued by Let's Encrypt; 988 certificates logged in CT; Certificates from 5 CAs: "CloudFlare, GlobalSign nv-sa, Google Trust Services.
Recommended actions
3 items
Steps to improve worldpossible.org's security grade, ranked by impact.
1
Set up email authentication (DMARC, DKIM)
Without email authentication, anyone can send emails that appear to come from worldpossible.org. This is the most common vector for phishing attacks targeting employees and customers. DMARC, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
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://worldpossible.org | grep -i strict
3
Add optional security headers (Referrer-Policy, Permissions-Policy)
worldpossible.org 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://worldpossible.org | 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
Not configured
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 include:_spf.google.com ~all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS configured with max-age=7889238s (91 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.
SSL Certificate
Valid
Strengths: Certificate valid, 85 days remaining; Issued by Let's Encrypt; 988 certificates logged in CT; Certificates from 5 CAs: "CloudFlare, GlobalSign nv-sa, Google Trust Services.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-d1.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d4.googledomains.com., ns-cloud-d3.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.