Skip to main content

Security report for alokranjan.me

Technology · Iceland

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

Security score

64/100

Risk levelMedium

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

The website alokranjan.me is a personal technology-focused site operated by an individual who identifies as a Linux enthusiast, Rust programmer, and cybersecurity aficionado. It serves as a portfolio and blog platform, targeting technology professionals and enthusiasts. The site features modern frontend technologies such as Tailwind CSS, Anime.js, and GSAP, hosted behind Cloudflare DNS and CDN services, ensuring good performance and mobile optimization. The content is well-structured, professional, and relevant to its niche audience. However, the site lacks formal privacy, cookie, and terms of service policies, which impacts its privacy compliance score. Security posture is moderate with HTTPS enabled but missing key security headers and DNSSEC. The WHOIS data indicates privacy protection but contains an anomalous domain creation date set in the future, which may be a data error or placeholder. Overall, the site is trustworthy for its intended purpose but could improve compliance and security practices.

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

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

Keep watching alokranjan.me

This scan found 22 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
70
DNS health
75
Network security
100
GDPR outside view
35
Average
64

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

This personal website operates as a small-scale technology blog and portfolio, focusing on open-source development, cybersecurity, and DevOps topics. It leverages GitHub for code hosting and blogging is planned or ongoing. The business model is personal branding and content sharing without commercial transactions. The target audience includes developers, Linux users, and cybersecurity professionals. The site maintains consistent branding and professional design, with clear navigation and contact channels primarily via email and a contact page. There are no indications of partnerships or subsidiaries. The domain is registered with privacy protection, which is typical for personal sites. The site’s market position is niche and specialized, catering to a tech-savvy audience.

Security posture

The website employs HTTPS with a valid SSL configuration and uses Cloudflare for DNS and CDN, which enhances security and performance. However, it lacks DNSSEC and common security headers such as Content-Security-Policy and X-Frame-Options, which could mitigate certain attack vectors. No vulnerability disclosure or security.txt files are present, limiting transparency for security researchers. The site does not expose sensitive data or use vulnerable libraries based on the analysis. Incident response contact channels are not provided. Overall, the security posture is moderate but could be significantly improved by implementing recommended headers, policies, and disclosure mechanisms.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security.
  2. Implement and publish a privacy policy and cookie consent mechanism to enhance privacy compliance.
  3. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Create a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Review and correct WHOIS domain creation date anomaly to ensure accurate domain registration data.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website of an individual who identifies as a linux nerd, rustacean, DevOps and cybersecurity enthusiast. The site includes blogs, projects, and contact information.
Key services
Blogging, Project showcase, Contact and networking
Content quality
good
Branding
consistent

Technology

Stack
Tailwind CSS, Anime.js, GSAP (GreenSock Animation Platform), Cloudflare DNS
Performance
fast
Mobile
excellent
Accessibility
good
SEO
basic

Security

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

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Insights
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal tech blog and portfolio with clear contact info.
  2. No privacy, cookie, or terms of service policies found.
  3. No security.txt or vulnerability disclosure information present.
  4. Uses modern frontend technologies and good mobile optimization.
  5. No phone numbers or physical addresses found.
  6. WHOIS data shows privacy protection and unusual future creation date.
  7. No signs of adult or questionable content.
  8. Minimal tracking via Cloudflare Insights only.
Technical notes

Notes

The website uses a modern frontend stack including Tailwind CSS for styling, Anime.js and GSAP for animations, and is served via Cloudflare DNS and CDN, contributing to fast load times and excellent mobile responsiveness. The HTML is valid and well-structured, with accessibility and SEO features at a basic to good level. The site includes interactive elements such as a terminal overlay and dynamic quote display. No CMS is detected, indicating a custom or static site approach. Tracking is minimal, limited to Cloudflare Insights. The site could benefit from enhanced SEO metadata and accessibility improvements to further boost technical maturity.
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 alokranjan.me. 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 alokranjan.me.

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.