Skip to main content

Security report for breezewiki.com

BreezeWiki developer (Cadence) · Technology · N/a

Medium risk. 10 critical or high findings in Security headers, GDPR outside view and 3 other checks.

Security score

58/100

Risk levelMedium

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

BreezeWiki is a small independent technology project founded in 2022 that offers an ad-free, streamlined mirror service for Fandom wiki pages. Its core value proposition is improving user experience by removing ads, videos, and suggested content, thereby enhancing page load speed and reducing data usage. The service is supported by multiple mirror sites and a browser extension for automatic redirection, targeting users who seek a cleaner alternative to Fandom's ad-heavy environment. The website is simple and content-focused, with clear navigation and good mobile optimization, but lacks formal privacy and cookie policies, which impacts compliance ratings. Technically, BreezeWiki uses basic HTML and CSS hosted on Vultr infrastructure with DNS managed via Vultr name servers. The domain is registered with Gandi SAS and is relatively new but consistent with the project's timeline. No advanced frameworks or CMS are detected, reflecting a lightweight and minimalistic approach. Performance is moderate with good mobile responsiveness, but accessibility and SEO optimizations are basic. Security posture is moderate; HTTPS is implied but no security headers or DNSSEC are enabled, and no vulnerability disclosure or incident response policies are published. From a security perspective, the site shows no signs of blocking or WAF interference, and no vulnerabilities or exposed sensitive data were detected in the content. However, the absence of privacy and cookie policies, security headers, and incident response information are notable gaps. The domain registration is consistent and legitimate for a small independent project, but enabling DNSSEC and adding security best practices would improve trust and resilience. Overall, BreezeWiki is a niche, small-scale service with a clear user-focused mission and moderate technical maturity. Strategic improvements in privacy compliance, security headers, and incident response transparency would enhance its security posture and user trust. The site is safe for general audiences and does not contain any adult or questionable content.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

10 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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

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

Keep watching breezewiki.com

This scan found 24 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
52
Security headers
15
Email security
65
DNS health
65
Network security
100
GDPR outside view
50
Average
58

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

BreezeWiki operates as a small independent technology service providing an alternative, ad-free browsing experience for Fandom wiki users. Its business model is based on free access supported by community goodwill rather than monetization. The project leverages open source principles, as evidenced by public source code and documentation. Its target customers are users frustrated by Fandom's ad-heavy interface. The service ecosystem includes multiple mirror sites and an affiliated browser extension partner (getindie.wiki) to facilitate automatic redirection. The project is positioned as a niche alternative rather than a direct competitor or replacement. Growth indicators include multiple mirrors and active developer engagement via mailing lists. No commercial partnerships or payment processing are evident. The project’s lean structure and lack of formal business registrations suggest a hobbyist or small-scale operation rather than a commercial enterprise.

Security posture

The security maturity of BreezeWiki is moderate. The domain is registered with a reputable registrar and has clientTransferProhibited status, which protects against unauthorized transfers. However, DNSSEC is not enabled, which is a missed opportunity to secure DNS integrity. The website uses HTTPS but lacks common security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security, which would mitigate common web attacks. No vulnerability disclosure policy or security.txt file is present, limiting formal incident response and reporting capabilities. No analytics or tracking scripts were detected, reducing privacy risks. The absence of privacy and cookie policies is a compliance gap, especially under GDPR. Overall, the site is low risk but would benefit from implementing security best practices and formal policies to improve resilience and user trust.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement key security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish privacy and cookie policies to improve GDPR compliance and user transparency.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible security reporting.
  5. Consider adding basic analytics with privacy-respecting configurations to monitor usage and improve service.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
BreezeWiki developer (Cadence)
Description
BreezeWiki provides a clean, ad-free mirror service for Fandom wiki pages by removing ads, videos, and suggested content to improve readability and performance.
Key services
Ad-free wiki page rendering, Mirror sites for redundancy, Browser extension for automatic redirection
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
excellent

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website provides a niche service as an ad-free mirror for Fandom wikis.
  2. No privacy, cookie, or terms of service policies found, which is a compliance gap.
  3. No explicit security policies or incident response information available.
  4. Contact is provided via developer personal site and mailing list.
  5. No commercial or payment processing information present.
  6. No analytics or tracking scripts detected in HTML content.
  7. Website is simple, clean, and focused on content delivery.
  8. No adult or questionable content detected.
  9. No WAF or blocking mechanisms detected.
  10. WHOIS data is consistent and domain is active with moderate expiry horizon.
Technical notes

Notes

The website is built with simple HTML and CSS without detectable use of advanced frameworks or CMS. Hosting is provided by Vultr, a reputable cloud provider, with DNS managed via Vultr name servers. The domain is registered with Gandi SAS and is relatively new (2022). The site is mobile responsive and has good navigation clarity but only basic SEO and accessibility features. No client-side scripts or analytics were detected in the provided HTML content, indicating a lightweight and privacy-conscious design. Performance is moderate, likely limited by the simplicity of the site and lack of advanced optimization techniques. The absence of security headers and DNSSEC represents technical debt and security risk. Overall, the technical infrastructure is minimal but functional for the service’s scope.
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 breezewiki.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 breezewiki.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.