Skip to main content

Security report for predr.ag

Netlify Inc · Technology · United States

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

Security score

62/100

Risk levelMedium

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

Predrag Gruevski's website is a personal blog and technical site focused on software development topics such as compilers and query systems. The site serves a niche audience of developers and technical conference attendees, offering blog posts, conference talks, and curated Twitter content. The business model is that of a personal content sharing platform, hosted on Netlify, with a domain registered under Netlify Inc. The domain age and registration details align well with the website's purpose and content. Technically, the site uses modern web standards including HTML5, CSS3, and JavaScript, and is hosted on Netlify's platform. The site performs well with fast loading times and good mobile optimization. SEO practices are adequate with proper meta tags and prerendering hints. Accessibility is basic but functional. No CMS or complex frameworks are detected. From a security perspective, HTTPS is enabled and domain transfer protections are in place. However, the site lacks DNSSEC, security headers, and published security or privacy policies. No contact information or incident response channels are provided, limiting transparency and trust. No vulnerabilities or malicious content were detected. The site does not use tracking or advertising technologies, enhancing privacy but also indicating limited commercial activity. Overall, the website is safe, professional, and trustworthy for its intended audience but would benefit from improved privacy compliance, security headers, and contact transparency to enhance credibility and security posture.

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

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 predr.ag

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

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 website operates as a personal technical blog by Predrag Gruevski, targeting software developers and technical audiences interested in compilers and query systems. It leverages Netlify's hosting platform and is registered under Netlify Inc, indicating a small-scale but professionally hosted operation. The business model is content-driven without evident monetization or advertising. The site maintains a focused niche presence with curated content and conference talks, suggesting a reputation-building or personal branding strategy rather than commercial scale. No partnerships or subsidiaries are evident. Growth indicators are limited due to lack of contact or business information. The site’s ecosystem is minimalistic, emphasizing content quality over commercial expansion.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and domain transfer protection. However, it lacks DNSSEC, security headers (such as CSP, HSTS), and published security or privacy policies. No vulnerability disclosure or incident response information is available, which could hinder timely reporting and resolution of security issues. The absence of contact information for security matters reduces transparency. No tracking or advertising scripts reduce privacy risks. Overall, the security maturity is moderate but could be significantly improved by implementing standard security headers, publishing policies, and providing clear security contact channels.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie policy to improve GDPR compliance and user trust.
  3. Add standard security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Content-Type-Options to harden the site against common attacks.
  4. Provide clear contact information including a security or abuse email address to facilitate incident reporting and response.
  5. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible security reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Netlify Inc
Description
Personal blog and site of Predrag Gruevski focusing on compilers, query systems, and software development topics.
Key services
Technical blog posts, Conference talks, Twitter content aggregation
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript
Platforms
Netlify
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

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 personal blog focused on software development and technical topics.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No security or incident response policies published.
  5. No advertising or tracking technologies detected.
  6. Site is hosted on Netlify with modern web technologies.
  7. Content is safe and appropriate for general audiences.
  8. No WAF or blocking mechanisms detected.
  9. WHOIS data is consistent and domain is relatively new but appropriate.
Technical notes

Notes

The website is built with clean, valid HTML5 and CSS3, and uses JavaScript for deferred script loading. It is hosted on Netlify, a modern cloud platform, which provides fast performance and good mobile optimization. The site uses prerender and prefetch hints to improve SEO and user experience. No CMS or complex frameworks are detected, indicating a lightweight and maintainable codebase. Accessibility is basic but functional. The site lacks advanced security headers and DNSSEC, which are technical gaps. Overall, the technical infrastructure is modern and performant but could benefit from enhanced security configurations and accessibility improvements.
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 predr.ag. 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 predr.ag.

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.