Skip to main content

Security report for orangc.net

orangc · Technology · Saudi Arabia

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

Security score

65/100

Risk levelMedium

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

The website orangc.net is a personal portfolio and project showcase for an individual developer named orangc, based in Riyadh, Saudi Arabia. The site highlights open source projects, personal notes, and social media presence, targeting a general audience interested in technology and open source software. The business model is that of a personal brand and developer portfolio with a small scale and focused content. Technically, the site is well implemented using modern web technologies, hosted on Cloudflare Pages, and optimized for performance and mobile devices. Security posture is good with HTTPS enforced and domain transfer protection enabled, but lacks DNSSEC and security headers. Privacy compliance is weak due to absence of privacy and cookie policies. Overall, the site is trustworthy and professional but could improve compliance and security practices. Strategic recommendations include adding privacy and cookie policies, enabling DNSSEC, and implementing security headers to enhance security and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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 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 orangc.net

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. 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
30
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
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

Orangc.net operates as a personal developer portfolio with a focus on open source projects and personal content. The site leverages a strong technical skill set in Python, Rust, and NixOS, and maintains a homelab infrastructure. The target audience includes developers, open source enthusiasts, and general internet users interested in technology. The business model is non-commercial and personal, with no evident revenue streams. The site demonstrates consistent branding and a clear presentation of projects and social links. The partnership ecosystem is limited to personal and open source communities. Growth indicators include active project maintenance and social media engagement. The site is positioned as a credible personal brand within the technology sector.

Security posture

The security maturity of orangc.net is moderate to good. The site enforces HTTPS and uses Cloudflare DNS and analytics services, which provide baseline security and performance benefits. The domain is protected against unauthorized transfers. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security reduces the overall security posture. No forms or input fields reduce attack surface, and no sensitive data is exposed. Privacy compliance gaps exist due to missing privacy and cookie policies. Incident response and vulnerability disclosure mechanisms are not present. Overall, the site is secure for its purpose but could benefit from enhanced security controls and compliance documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and cookie policy to improve GDPR and privacy compliance.
  3. Implement standard security headers including Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  5. Consider implementing a cookie consent mechanism if any cookies beyond analytics are used.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
orangc
Description
Personal website of orangc, a Muslim student and developer based in Riyadh, Saudi Arabia. The site showcases personal projects, social links, and notes.
Key services
Open source software projects, Personal notes and blog, Homelab and server status dashboard
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS (Tailwind CSS or similar utility classes), JavaScript, Python (mentioned as developer skill), TypeScript (for some projects), Nextcord (Discord bot framework), Pycord (Discord bot framework), NixOS (hosting and environment), Cloudflare (DNS and analytics)
Frameworks
Nextcord, Pycord
Platforms
Cloudflare Pages
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Umami, Cloudflare Pages Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Pages Analytics, Umami Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal portfolio and project showcase for a developer named orangc.
  2. No privacy or cookie policies found, which is a compliance gap.
  3. No forms detected; no data collection beyond analytics scripts.
  4. Strong presence of open source projects and social media links.
  5. Good technical implementation with modern frontend and hosting on Cloudflare Pages.
  6. No security headers detected in HTML but HTTPS is enforced.
  7. No signs of adult or questionable content.
  8. WHOIS data is consistent and domain is not privacy protected.
  9. Analytics usage is minimal and privacy compliance could be improved.
Technical notes

Notes

The website is built with modern frontend technologies including HTML5, CSS with utility classes (likely Tailwind CSS), and JavaScript. It uses Cloudflare Pages for hosting and DNS, providing fast performance and global CDN benefits. The site is mobile optimized and accessible with clear navigation and structured content. No CMS is detected, indicating a static or custom-built site. Analytics are implemented via Umami and Cloudflare Pages Analytics, with minimal user tracking. The technical stack aligns well with the personal portfolio use case, with no detected technical debt or legacy components. Opportunities exist to enhance security headers and DNS configuration for improved resilience.
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 orangc.net. 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 orangc.net.

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.