Skip to main content

Security report for bloggrify.com

Bloggrify · Technology · N/a

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

Security score

65/100

Risk levelMedium

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

Bloggrify is an open-source static blog generator platform designed primarily for developers seeking a fast, efficient, and maintenance-free blogging solution. It leverages modern web technologies such as Nuxt.js, Vue.js, and Tailwind CSS to provide a developer-friendly experience with built-in SEO, analytics, and theming capabilities. The platform targets technical users who prefer markdown-based content management and static site hosting. Technically, the website employs a modern tech stack and supports multiple hosting providers, but performance is moderate and accessibility is basic. Security posture is weak due to the absence of a valid SSL/TLS certificate and HTTPS support, which is a critical issue. No privacy or cookie policies are present, and no contact information is publicly available, which impacts privacy compliance and business credibility. Overall, the site is functional and professional in design but requires significant improvements in security and privacy compliance to enhance trust and user safety.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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 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

    • 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 bloggrify.com

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
97
Security headers
40
Email security
40
DNS health
85
Network security
100
GDPR outside view
25
Average
65

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

Bloggrify occupies a niche market as a static site generator focused on developer experience and performance. Its open-source business model relies on community contributions and optional paid themes. The platform's competitive advantages include zero-maintenance operation, Git-based content workflow, and integrated essential features like SEO and analytics. The target customers are developers and technical teams who value speed, simplicity, and cost-effectiveness. The project demonstrates growth potential through community engagement on GitHub and social media. Partnerships with analytics providers like Blogtally and Pirsch enhance its ecosystem. However, the lack of explicit business contact information and privacy policies may limit broader adoption in regulated markets.

Security posture

The website's security maturity is low due to the lack of HTTPS and valid SSL/TLS certificates, exposing users to potential interception risks. While HSTS is enabled, it is ineffective without HTTPS. No advanced security headers beyond HSTS are detected. The absence of privacy and cookie policies indicates compliance gaps with GDPR and other data protection regulations. No incident response or vulnerability disclosure information is available, limiting transparency. The site does not expose sensitive data or show signs of vulnerable libraries, but the missing encryption is a critical vulnerability. Overall, the security posture requires urgent enhancement to protect user data and build trust.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS across the site immediately.
  2. Add comprehensive privacy and cookie policies with clear consent mechanisms to comply with GDPR.
  3. Publish contact information including security incident response contacts to improve transparency.
  4. Enhance security headers by adding Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  5. Regularly audit dependencies and update to mitigate potential vulnerabilities.
Technical notes

Notes

The website is built on a solid modern infrastructure using Nuxt.js and Vue.js frameworks, with Tailwind CSS for styling and Markdown for content management. It integrates advanced features such as syntax highlighting with Shiki, math rendering with KaTeX, and diagram support via Mermaid. Hosting is on AWS infrastructure, and the site supports deployment on popular static hosting platforms. Performance is moderate with a page load time of approximately 5.5 seconds and 80 resources loaded, indicating room for optimization. SEO is well addressed with Open Graph and Twitter meta tags. However, the lack of HTTPS and incomplete security configurations present technical risks that could impact user trust and search engine rankings.
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 bloggrify.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 bloggrify.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.