Skip to main content

Security report for opendomain.org

OpenDomain · Other · United States

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

Security score

52/100

Risk levelMedium

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

OpenDomain is a small US-based entity founded in 2004 that offers free use of domains they own but do not actively develop. Their business model is non-commercial, focusing on supporting open source communities by providing domain usage rights without transfer or sale. The website is built on WordPress and uses Cloudflare for DNS services. The technical infrastructure is moderate with basic mobile optimization and SEO. Security posture is adequate with HTTPS enabled and domain transfer protection, but lacks DNSSEC and security headers. Privacy compliance is weak due to absence of privacy and cookie policies. No contact information or incident response details are provided, limiting trust and compliance. Overall, the site is functional and safe but would benefit from enhanced security and compliance measures.

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 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 opendomain.org

This scan found 25 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
52
Security headers
30
Email security
70
DNS health
70
Network security
40
GDPR outside view
50
Average
52

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

OpenDomain occupies a niche market position as a provider of free domain usage for open source projects, leveraging a sharing philosophy. The business model is unique and non-commercial, targeting open source groups and responsible users. The company has no visible partnerships or subsidiaries and does not engage in advertising or analytics tracking. Growth indicators and revenue streams are not evident. The website content is basic but relevant to its mission. The lack of contact details and compliance documentation may limit broader adoption or trust.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and domain transfer protection status set. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security reduces defense-in-depth. No vulnerability disclosures or incident response contacts are published, indicating limited security maturity. The WordPress CMS requires regular updates to mitigate risks. No exposed sensitive data or known vulnerabilities were detected in the content. Overall, security is functional but could be significantly improved to meet best practices and compliance standards.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR and privacy compliance.
  4. Add clear contact information including security incident response contacts to improve trust and readiness.
  5. Regularly update WordPress core and plugins and conduct security audits to reduce vulnerability risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OpenDomain
Description
OpenDomain provides free use of domains they own but do not currently develop, promoting open source and sharing principles. They offer domains for free use under simple terms without transfer or sale.
Key services
Provision of free domains for use under open source principles
Content quality
basic
Branding
consistent

Technology

Stack
WordPress, Cloudflare DNS, JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

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

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is accessible and not blocked by WAF or security mechanisms.
  2. No privacy or cookie policies found, which is a compliance gap.
  3. Terms of Service page is present and linked.
  4. No contact emails or phone numbers explicitly provided on the homepage.
  5. Site uses WordPress CMS with standard theme 'twentynineteen'.
  6. No analytics or advertising scripts detected.
  7. No social media links or business contact information found.
  8. Content is focused on offering free domain usage for open source projects.
  9. No security headers detected in HTML content; DNSSEC not enabled.
  10. SSL is enabled and domain status is clientTransferProhibited, indicating domain transfer protection.
Technical notes

Notes

The website uses WordPress CMS with the default 'twentynineteen' theme and is hosted behind Cloudflare DNS services. The site loads JavaScript for emoji support and uses standard CSS stylesheets. Performance is moderate with basic mobile optimization and accessibility features. SEO is basic with meta tags and canonical links present. No advanced frameworks or analytics tools are detected. The technical stack is simple and stable but could benefit from modernization and enhanced security configurations.
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 opendomain.org. 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 opendomain.org.

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.