Skip to main content

Security report for kitsu.page

Technology · N/a

Medium risk. 8 critical or high findings in Email security, Security headers and 1 other check.

Security score

52/100

Risk levelMedium

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

KitsuPage is a small technology service offering free static hosting for user repositories, leveraging Git branches to serve content automatically. The service targets developers and users seeking simple, no-cost static site hosting with optional custom domain support. The website is minimalistic, providing essential information about usage and configuration but lacks comprehensive business or legal documentation. Technically, the site uses basic HTML and CSS without advanced frameworks or CMS, and no analytics or advertising scripts are present, indicating a lightweight and privacy-conscious approach. Security posture is limited with no visible security headers or privacy policies, and no contact information is provided except for an abuse report link. The domain uses privacy protection, which is typical for small tech projects, and no suspicious WHOIS patterns were detected. Overall, the site is functional but basic, with room for improvement in security, compliance, and user engagement.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 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

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…
  3. 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

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

Keep watching kitsu.page

This scan found 23 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. See sample alerts.

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
95
Security headers
20
Email security
40
DNS health
75
Network security
40
GDPR outside view
40
Average
52

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

KitsuPage operates in the niche market of free static hosting services, differentiating itself by automatic deployment from Git branches and integration with the KitsuDev platform. Its business model appears to be service-based with no direct monetization visible on the site. The target audience is developers and hobbyists needing simple hosting solutions. The presence of source code links and abuse reporting indicates a community-driven or open-source ethos. The lack of detailed business information, contact data, or certifications suggests a small-scale operation with limited formal structure. Growth potential may depend on expanding features, improving security and compliance, and increasing visibility within developer communities.

Security posture

The website demonstrates a low to moderate security maturity level. It uses HTTPS (implied by URL scheme), but no security headers such as Content-Security-Policy or X-Frame-Options are present in the HTML content. There are no visible forms or input fields, reducing attack surface, but also no explicit security policies or incident response contacts beyond an abuse report page. The absence of privacy and cookie policies indicates compliance gaps with GDPR and other regulations. No vulnerabilities or exposed sensitive data were detected in the provided content. Overall, the security posture is minimal and would benefit from enhanced policies, headers, and transparency.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve compliance and user trust.
  2. Implement standard security headers (CSP, X-Frame-Options, HSTS) to enhance protection against common web attacks.
  3. Provide clear contact information for security incidents and general inquiries to improve transparency and incident response readiness.
  4. Enhance SEO and accessibility features to improve user experience and reach.
  5. Consider adding analytics with privacy-respecting configurations to better understand user engagement and improve service.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Free, static hosting service that automatically serves user repositories as static websites.
Key services
Static site hosting, Custom domain support
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website provides a free static hosting service with Git branch based deployment.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails or phone numbers explicitly provided.
  4. Source code and abuse report links are provided, indicating some transparency.
  5. No analytics or advertising scripts detected, indicating minimal tracking.
  6. No security headers or advanced security features detected in the HTML content.
  7. No forms or data collection mechanisms present on the page.
  8. Content is minimal but functional and targeted at developers.
  9. No social media links or company contact information found.
  10. No explicit or adult content detected; content is safe for general audiences.
Technical notes

Notes

The website is built with basic HTML5 and CSS, without use of JavaScript frameworks or CMS platforms. It serves static content with minimal dependencies, which supports fast loading and low complexity. However, the lack of meta tags beyond the title and viewport limits SEO effectiveness. No performance optimization or accessibility features are explicitly implemented. Hosting provider details are not disclosed. The technical setup is suitable for a small-scale static hosting service but could be modernized with improved metadata, responsive design enhancements, and security best practices.
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 kitsu.page. 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 kitsu.page.

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.