Skip to main content

Security report for pika.page

Good Enough · Technology · N/a

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

Security score

67/100

Risk levelMedium

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

Pika.page is a small technology company offering a blogging platform designed to provide a happy and simple blogging experience. The platform is built using modern web technologies such as Ruby on Rails, Hotwired Turbo, and Stimulus, with a focus on performance and mobile optimization. The website demonstrates good design quality and user experience, with clear navigation and relevant content for bloggers and content creators. Security posture is adequate with HTTPS and CSRF protections in place, but lacks visible security policies and incident response information. Privacy compliance is minimal due to the absence of privacy and cookie policies. Overall, the website appears legitimate and trustworthy, with consistent WHOIS data matching the company branding.

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 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

    • High

      Third-party services without privacy policy

      Detected services: Twitter

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching pika.page

This scan found 21 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
72
Security headers
65
Email security
50
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

The company 'Good Enough' positions itself as a niche blogging platform provider targeting bloggers and content creators seeking a straightforward and pleasant blogging experience. The business model revolves around providing blogging services with content creation tools. The platform leverages modern web frameworks and libraries, indicating a commitment to technical quality. There is no evidence of advertising or extensive tracking, suggesting a user-friendly and privacy-conscious approach. The lack of detailed business contact information and policies may limit trust for some users. The company appears to be a small-sized entity with no publicly disclosed subsidiaries or parent companies.

Security posture

The website employs HTTPS with a valid SSL configuration and includes CSRF tokens to protect forms, reflecting good baseline security practices. However, it lacks important security headers such as Content-Security-Policy and X-Frame-Options, which could enhance protection against common web attacks. No vulnerabilities or exposed sensitive data were detected in the provided content. The absence of a security policy, incident response contacts, or vulnerability disclosure mechanisms indicates room for improvement in security governance and transparency. Overall, the security posture is moderate but could be strengthened by adding visible policies and security headers.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve privacy compliance.
  2. Add security headers like Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance security posture.
  3. Provide clear contact information including support and incident response channels to improve business credibility and incident handling.
  4. Consider publishing a vulnerability disclosure policy or security.txt file to foster responsible security reporting.
  5. Enhance accessibility features and conduct regular security audits to maintain and improve technical and security standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Good Enough
Description
Pika is a pretty good blogging platform built by the good people at Good Enough.
Key services
blog hosting, content creation tools
Content quality
good
Branding
consistent

Technology

Stack
Ruby on Rails, Turbo Rails, Stimulus, Tagify, Tiptap Editor, FontAwesome, JavaScript ES Modules, CDN for JS libraries
Frameworks
Ruby on Rails, Hotwired Turbo, Stimulus
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • CSRF token implemented

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a niche blogging platform with a focus on simplicity and user happiness.
  2. No explicit privacy, cookie, or terms of service policies found on the main page.
  3. No contact emails or phone numbers explicitly provided in the HTML content.
  4. Modern JavaScript frameworks and libraries are used, indicating up-to-date technical implementation.
  5. Security practices like HTTPS and CSRF tokens are implemented but lack visible security policies.
  6. No advertising or tracking scripts detected, indicating minimal user tracking.
  7. No signs of WAF or content blocking; site is fully accessible.
Technical notes

Notes

The website is built on a modern Ruby on Rails stack with Hotwired Turbo and Stimulus for frontend interactivity, supported by various JavaScript libraries such as Tagify and Tiptap editor extensions. The use of ES modules and CDN-hosted libraries indicates a contemporary approach to web development. Performance is moderate with good mobile optimization. The site lacks some advanced accessibility features and SEO enhancements but includes proper meta tags and Open Graph data for social sharing. Hosting provider details are not disclosed. Overall, the technical infrastructure is solid with opportunities for further modernization and security hardening.
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 pika.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 pika.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.