Skip to main content

Security report for cleandns.space

Technology · N/a

Medium risk. 9 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

60/100

Risk levelMedium

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

CleanDNS is a technology-focused service specializing in tracking domains that engage in abusive activities. The website serves primarily as a login portal for users, with minimal public-facing content describing the business. The target audience likely includes security professionals and organizations interested in domain abuse monitoring. The site uses modern web technologies including React and Vite, and integrates Google Analytics for user tracking. However, the public content is limited, and critical compliance documents such as privacy and cookie policies are absent. From a technical perspective, the website demonstrates moderate digital maturity with a modern JavaScript stack and module loading. Performance and mobile optimization are basic but functional. Security posture shows room for improvement; while HTTPS is implied, no security headers or vulnerability disclosure mechanisms are evident. The login form is present but disabled, indicating incomplete or restricted access. Privacy compliance is weak due to missing policies and consent mechanisms. Overall, the security posture is moderate but lacks transparency and comprehensive policies. The domain registration uses privacy protection, which aligns with the security nature of the service but reduces public trust signals. No suspicious or malicious indicators were found. The site is safe for general audiences and contains no adult or questionable content. Strategic recommendations include implementing clear privacy and cookie policies, enhancing security headers, enabling secure login functionality, and adding vulnerability disclosure information to improve trust and compliance.

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

9 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 cleandns.space

This scan found 27 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
72
Security headers
15
Email security
70
DNS health
65
Network security
100
GDPR outside view
35
Average
60

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

CleanDNS operates in the niche domain abuse tracking market, targeting security-conscious organizations and professionals. The business model appears to be service-based, likely subscription or access-controlled, given the login portal. The company maintains a consistent brand identity but lacks public business details such as company name, registration, or contact information, which may limit trust for new users. The use of privacy-protected WHOIS data is common in security services but reduces transparency. The integration with cleandns.com suggests a broader ecosystem or parent service. Growth potential depends on expanding public trust signals and improving user engagement through accessible information and compliance documentation.

Security posture

The website's security maturity is moderate. HTTPS is used, and password inputs are secured, but no security headers were detected in the provided data. The absence of privacy and cookie policies indicates compliance gaps with GDPR and other regulations. The disabled login buttons suggest restricted or incomplete access control mechanisms. No incident response or security contact information is provided, limiting the ability to report or respond to security issues. The use of Google Analytics introduces moderate user tracking without visible consent mechanisms, which may pose privacy concerns. Overall, the site would benefit from enhanced security policies, headers, and transparency to strengthen its security culture and compliance posture.

Recommendations

  1. Implement and publicly display comprehensive privacy and cookie policies with GDPR compliance details.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve security posture.
  3. Enable and secure the login functionality with proper validation and user feedback.
  4. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Enhance accessibility and SEO metadata to improve user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
CleanDNS appears to be a service focused on tracking domains engaging in abuse.
Key services
Tracking domains engaging in abuse
Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, Vite, Google Analytics (gtag.js)
Frameworks
React
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
50/100
Good practices seen
  • HTTPS usage implied by URL (https://)
  • Use of secure input fields (password type)

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a login portal for CleanDNS service with minimal public content
  2. No privacy, cookie, or terms of service policies found on the main page
  3. Uses Google Analytics for tracking
  4. No visible contact emails or phone numbers; only a login form is present
  5. No social media links detected
  6. Site uses modern JavaScript frameworks and module loading
  7. Security headers and policies are not visible in provided data
  8. No signs of WAF or blocking mechanisms
Technical notes

Notes

The website is built using modern JavaScript technologies including React and Vite, with module-based script loading. Google Analytics is integrated for user behavior tracking. The site design is basic but consistent, with a focus on a login portal. Performance is moderate with no evident broken elements. Mobile optimization and accessibility are basic but present. No CMS or hosting provider information is discernible from the provided data. The lack of SEO metadata and structured data limits search engine visibility. Technical debt appears low but the absence of security headers and compliance documentation indicates areas for modernization and risk mitigation.
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 cleandns.space. 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 cleandns.space.

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.