Skip to main content

Security report for copy.sh

Domain Protection Services, Inc. · Technology · United States

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 copy.sh is a personal project site operated by an individual developer with interests in programming languages such as OCaml, K, Rust, and JavaScript. The site hosts browser-based emulators, games, and programming tools, targeting developers and hobbyists interested in emulation, simulations, and code golf. The business model is primarily personal and open source, with no commercial transactions or services offered. The domain is registered through a domain protection service, consistent with privacy-conscious personal use, and has been active since 2012. Technically, the site is built with standard HTML, CSS, and JavaScript, hosted behind Cloudflare DNS. The site is fast and mobile responsive at a basic level, with clean and structured content. However, there is no evidence of advanced frameworks or CMS usage. SEO and accessibility are basic but adequate for the site's scope. No analytics or tracking technologies are detected, indicating a privacy-respecting approach. From a security perspective, the domain is locked against transfer, but DNSSEC is not enabled. The site lacks security headers such as CSP or HSTS, and no privacy or cookie policies are present, which reduces compliance with GDPR and other privacy regulations. No forms or data collection mechanisms are present, minimizing attack surface. Overall, the security posture is moderate but could be improved with standard best practices. The overall risk is low given the non-commercial, personal nature of the site and minimal data collection. Strategic recommendations include enabling DNSSEC, adding security headers, publishing privacy and cookie policies, and considering a vulnerability disclosure policy to enhance trust 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 copy.sh

This scan found 23 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
95
Security headers
15
Email security
70
DNS health
55
Network security
100
GDPR outside view
50
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

copy.sh operates as a niche personal website focused on programming and emulation projects. Its market positioning is that of a hobbyist and open source contributor rather than a commercial entity. The site leverages open source code repositories on GitHub and shares projects freely, appealing to a technical audience of developers and enthusiasts. Revenue streams or partnerships are not evident. The site’s longevity since 2012 indicates stable maintenance. The partnership ecosystem is minimal, with no formal partners or subsidiaries. The business model is content and project sharing without monetization. Growth indicators are limited but consistent with a personal project site.

Security posture

The security maturity level is moderate. The domain is protected against unauthorized transfer, but DNSSEC is not enabled, which is a recommended security enhancement. The website lacks HTTP security headers, which could mitigate common web attacks. No privacy or cookie policies are published, indicating a compliance gap with GDPR and similar regulations. No incident response or vulnerability disclosure information is provided, limiting transparency. The absence of forms reduces risk exposure. Overall, the site is low risk but would benefit from adopting standard security best practices and compliance documentation to improve trustworthiness and resilience.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security.
  2. Implement HTTP security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  3. Publish a privacy policy and cookie policy to enhance GDPR compliance and user trust.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Consider adding incident response contact information to improve transparency and readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Domain Protection Services, Inc.
Description
Personal website of a developer interested in OCaml, K, Rust, JS, emulators, simulations, browser games, array programming, and code golf. Offers browser-based emulators, games, and programming tools.
Key services
Browser-based OS emulators, Platformer game, Game of Life implementation, Brainfuck editor and interpreter, Code golf challenges and programming resources
Content quality
good
Branding
consistent

Technology

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

Security

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

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. No privacy, cookie, or terms of service policies found.
  2. Contact email is provided clearly on homepage.
  3. No phone numbers or physical addresses found.
  4. No social media links except GitHub and Twitch mentioned in comments.
  5. No forms or data collection mechanisms detected.
  6. Website is a personal project site with open source software and games.
  7. No advertising or tracking technologies detected.
  8. No security headers detected in HTML content.
  9. DNSSEC not enabled, but domain transfer locked.
  10. No explicit SSL/TLS info available from provided data.
Technical notes

Notes

The website uses a simple and clean technical stack based on HTML5, CSS3, and JavaScript without heavy frameworks or CMS. Hosting is via Cloudflare DNS, but no direct hosting provider details are available. The site loads quickly and is mobile responsive at a basic level. SEO and accessibility are basic but functional. There is no evidence of analytics or tracking scripts, which aligns with privacy respect. The lack of security headers and DNSSEC represents technical debt and security risk. The site’s technical simplicity reduces complexity but also limits advanced features or integrations.
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 copy.sh. 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 copy.sh.

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.