Skip to main content

Security report for everybodywiki.com

Other · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

67/100

Risk levelMedium

0–100, higher is better. How it is calculated

The website everybodywiki.com is currently inaccessible due to a Cloudflare security challenge page that requires human verification before access. This prevents retrieval of actual business content, contact information, or policies. The domain is registered with OVH sas since 2017 and uses Cloudflare for DNS and security services. The technical infrastructure includes Cloudflare Turnstile captcha and Cloudflare Insights for performance monitoring. Security posture is moderate with HTTPS enabled and domain status protections, but DNSSEC is not enabled and no security headers are visible in the HTML content. Privacy and cookie policies, terms of service, and contact information are not present on the accessible page. Overall, the site appears to be protected by a WAF, limiting content visibility and analysis.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

7 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching everybodywiki.com

This scan found 19 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
60
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
35
Average
67

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Due to the Cloudflare challenge page, no direct business information, company name, or service descriptions are available. The domain age suggests an established presence since 2017. The lack of visible business data, contact details, or social media links limits assessment of market positioning, business model, or partnerships. The use of Cloudflare indicates a focus on security and performance. No evidence of advertising or affiliate programs was found. The website likely targets a general audience but no content is accessible to confirm this.

Security posture

The website benefits from HTTPS and domain status protections that prevent unauthorized domain transfer or deletion. However, DNSSEC is not enabled, which is a recommended security enhancement. The presence of a Cloudflare WAF and Turnstile captcha indicates active protection against automated threats and abuse. No privacy or security policies are visible, and no incident response contacts are provided. The lack of security headers in the HTML content is a weakness. Overall, the security posture is moderate but could be improved with DNSSEC, security headers, and transparency in policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish clear privacy, cookie, and terms of service policies to improve compliance and user trust.
  3. Add visible contact information and incident response contacts to support transparency and security reporting.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the website.
  5. Consider reducing WAF challenge frequency or providing alternative access methods to improve user experience and enable content analysis.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Detected Cloudflare security challenge page with Turnstile captcha and verification message blocking access to actual content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
moderate

Technology

Stack
Cloudflare Turnstile, Cloudflare Insights
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
55/100
Good practices seen
  • HTTPS enabled
  • Domain status clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Insights
Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is blocked by Cloudflare security challenge
  2. No visible business or contact information on the page
  3. No privacy, cookie, or terms of service policies found
  4. No forms or data collection fields visible except hidden Turnstile response input
  5. No social media or external business links found
  6. Website uses Cloudflare for security and performance
  7. WHOIS data shows domain is registered and active with no privacy protection
  8. DNSSEC is not enabled, which is a security improvement opportunity
  9. Page title and content indicate verification step, no actual business content accessible
Technical notes

Notes

The website uses Cloudflare services including Turnstile captcha for bot mitigation and Cloudflare Insights for performance monitoring. The domain is hosted via OVH sas with Cloudflare DNS. The HTML content is minimal and serves only as a security challenge page, lacking any business or navigational content. The site is mobile responsive at a basic level but lacks SEO optimization and accessibility features. No CMS or frameworks are detected from the HTML. Performance is moderate given the security challenge overhead. The technical setup prioritizes security but limits content accessibility.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with everybodywiki.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review everybodywiki.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.