Skip to main content

Security report for p3k.io

Privacy service provided by Withheld for Privacy ehf · Technology · Iceland

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

Security score

52/100

Risk levelMedium

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

The website indieweb.org/p3k serves as a documentation and informational hub for the p3k software, a personal publishing platform used by members of the IndieWeb community. It provides detailed technical descriptions, open source component links, and development updates. The site is built on MediaWiki and hosted on Linode, leveraging modern web technologies and minimal user tracking via Fathom Analytics. The target audience is primarily developers and IndieWeb enthusiasts interested in personal publishing tools and standards. Technically, the site demonstrates good infrastructure with HTTPS enabled and fast performance. However, it lacks some security best practices such as DNSSEC and security headers. Privacy compliance is basic, with a privacy policy present but no cookie consent mechanism. Contact and incident response information are absent, which limits transparency and user trust in security matters. From a security perspective, the site shows a moderate posture with no critical vulnerabilities detected but room for improvement in headers and policies. The domain registration is privacy protected but consistent with the nature of the project. Overall, the site is trustworthy and professional but could enhance compliance and security transparency. Strategic recommendations include enabling DNSSEC, implementing security headers, adding cookie consent mechanisms, and publishing incident response and vulnerability disclosure policies to improve user trust and compliance posture.

Scanned

This is an earlier scan of p3k.io. View the latest report

NIS2 and GDPR posture

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

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 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 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 p3k.io

This scan found 26 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
42
Security headers
30
Email security
70
DNS health
70
Network security
40
GDPR outside view
58
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention p3k.io, from OffSeq Breach.

No leaked records found

Breach holds no records for p3k.io right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

The p3k project is a niche open source software initiative within the IndieWeb ecosystem, focusing on personal publishing platforms. It operates with a community-driven model, offering reusable software components rather than a commercial product. The project targets developers and IndieWeb users seeking customizable publishing tools. Its market position is specialized with limited direct competition, relying on community adoption and contributions. The project is supported by a small team or individual, with no evident commercial revenue streams. Partnerships are primarily within the IndieWeb community and open source contributors. Growth indicators include active GitHub repositories and ongoing feature development.

Security posture

The website maintains a moderate security maturity level with HTTPS enforced and domain transfer protection enabled. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options reduces its defense-in-depth. No incident response or vulnerability disclosure information is provided, which could delay mitigation of potential issues. Privacy compliance is minimal, lacking cookie consent mechanisms despite having a privacy policy. No exposed sensitive data or vulnerable libraries were detected. Overall, the security posture is adequate for a community documentation site but should be enhanced to meet higher compliance and trust standards.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a cookie consent banner or mechanism to comply with privacy regulations and improve transparency.
  4. Publish clear incident response and vulnerability disclosure policies with contact channels.
  5. Enhance privacy policy to explicitly address GDPR compliance and data retention practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Privacy service provided by Withheld for Privacy ehf
Description
pзk (pronounced "peek") is the name of the software that runs aaronparecki.com and indiewebcat.com. It is a personal publishing platform software with components open sourced for reuse.
Key services
Personal publishing platform software, Open source components for IndieWeb, APIs and tools for location, posting, webmentions, and Microsub
Content quality
good
Branding
consistent

Technology

Stack
MediaWiki 1.41.0, JavaScript, PHP, MySQL, YAML, Markdown
Frameworks
MediaWiki
Platforms
Web
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • ClientTransferProhibited domain status

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Fathom Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a MediaWiki-based community and documentation site for p3k software.
  2. Content is technical and developer-focused with open source components.
  3. No direct business contact information or commercial services advertised.
  4. No privacy or cookie consent banners detected despite privacy policy presence.
  5. Uses HTTPS with no visible security headers; DNSSEC not enabled.
  6. WHOIS privacy protection used, appropriate for this type of project.
  7. Includes links to multiple external IndieWeb-related domains and GitHub repositories.
  8. Uses Fathom Analytics for minimal user tracking.
  9. No forms collecting personal data detected on the page.
  10. No incident response or vulnerability disclosure information found.
Technical notes

Notes

The website is powered by MediaWiki 1.41.0, a mature and widely used wiki platform. It uses PHP and MySQL backend with JavaScript for client-side interactions. The site is hosted on Linode, a reputable cloud hosting provider. Performance is fast with minimal scripts and efficient content delivery. The site is mobile optimized and accessible with clear navigation and structured content. SEO is supported by proper meta tags and Open Graph data. The technical stack is modern and well-maintained, though some security hardening is recommended. The use of Fathom Analytics indicates a privacy-conscious approach to user tracking.
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

Earlier scans of this domain

  1. 66/100Medium30 findingsView report
Reviews of this site

Share your experience with p3k.io. 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 p3k.io.

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.