Skip to main content

Security report for pageview.click

Technology · N/a

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

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

Pageview.click is a newly launched website analytics service targeting indie hackers and small website owners who seek affordable and privacy-conscious traffic analytics. The service emphasizes low operational costs and aggregate data privacy, positioning itself as a cost-effective alternative to expensive analytics platforms. The website presents real-time and historical traffic data with a clean, modern design and uses contemporary web technologies such as Nuxt.js and Vue.js, hosted behind Cloudflare DNS services. From a technical perspective, the site demonstrates good performance, mobile optimization, and accessibility. The use of TailwindCSS and server-side rendering frameworks indicates a modern and maintainable infrastructure. However, the absence of explicit privacy and cookie policies, as well as lack of contact information and security headers, suggests room for improvement in compliance and security transparency. Security posture is moderate with HTTPS enforced and domain-level protections like clientTransferProhibited status, but DNSSEC is not enabled and no security policies or incident response information are published. No vulnerabilities or suspicious patterns were detected, and the domain registration is consistent with the business age and claims. Overall, the website is functional, professional, and safe for general audiences but would benefit from enhanced privacy compliance, security transparency, and contact information to improve trust and regulatory adherence.

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

9 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 pageview.click

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. 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
75
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
35
Average
60

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

Pageview.click operates in the technology sector, specifically in web analytics services. Its market positioning targets indie hackers and small website owners who require affordable analytics solutions. The business model is based on providing low-cost or nearly free analytics services, leveraging low operational costs. The company appears to be a small startup founded in 2024, with no parent or subsidiary companies identified. The service offers aggregate traffic statistics and real-time page view data, which may appeal to a niche segment underserved by larger analytics providers. The partnership ecosystem is minimal, with no explicit partners or subsidiaries listed. Growth indicators include active uptime of analytics instances and a growing dataset of monthly page views. Strategic observations suggest focusing on expanding privacy and security features to enhance market credibility.

Security posture

The security maturity level of Pageview.click is moderate. The site enforces HTTPS and uses reputable DNS and hosting providers (Cloudflare). Domain registration includes protective statuses to prevent unauthorized transfers or deletions. However, the absence of DNSSEC and lack of published security policies or incident response procedures indicate gaps in security governance. No exposed sensitive data or vulnerable libraries were detected in the analysis. Privacy compliance is limited due to missing privacy and cookie policies. Incident response readiness and vulnerability disclosure mechanisms are not publicly available, which could impact trust and regulatory compliance. The security culture appears nascent, typical for a new startup, with opportunities to improve transparency and formalize security practices.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to improve GDPR and privacy compliance.
  3. Add explicit security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options.
  4. Provide clear contact information including security and general inquiry emails to improve trust and incident response capabilities.
  5. Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Pageview.click provides website traffic analytics services focused on affordable and privacy-conscious analytics for indie hackers and small websites.
Key services
Website traffic analytics, Aggregate traffic statistics
Content quality
good
Branding
consistent

Technology

Stack
TailwindCSS, Vue.js (number-flow-vue component), Cloudflare DNS, Nuxt.js (server-side rendering framework)
Frameworks
Nuxt.js, Vue.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by Cloudflare usage and script URLs)
  • Domain status includes clientTransferProhibited and clientDeleteProhibited

Analytics and tracking

Services
Pageview.click own analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website provides real-time and historical website traffic analytics data.
  2. No privacy or cookie policies found on the site.
  3. No contact emails or phone numbers explicitly provided.
  4. Site uses modern frontend technologies and good design practices.
  5. No explicit security or incident response policies published.
  6. No advertising or third-party tracking detected beyond own analytics.
  7. Domain is very new but consistent with business claims.
  8. No signs of adult or questionable content.
Technical notes

Notes

The website is built using modern frontend technologies including Nuxt.js and Vue.js, styled with TailwindCSS. It leverages Cloudflare for DNS and likely CDN services, contributing to fast loading times and good mobile optimization. The site uses server-side rendering for SEO benefits and dynamic data presentation. Performance is fast with responsive design and accessibility features. However, the absence of CMS or backend platform details limits deeper technical insight. No broken elements or errors were detected. Opportunities exist to improve technical security by adding security headers and enabling DNSSEC. Overall, the technical infrastructure is solid for a startup analytics service.
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 pageview.click. 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 pageview.click.

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.