Skip to main content

Security report for ntldstats.com

greenSec GmbH · Technology · Germany

High risk. 7 critical or high findings in Network security, Security headers and 2 other checks.

Security score

46/100

Risk levelHigh

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

nTLDStats is a specialized service providing statistical data and analytics related to new top-level domains. The business is operated by greenSec GmbH, a small technology company based in Germany founded in 2014. The website is positioned as a niche provider targeting domain investors, registrars, and cybersecurity professionals interested in domain market insights. The business model revolves around offering domain statistics and analytics services. Technically, the website uses older frontend libraries such as Bootstrap 3.1.1 and Font Awesome 4.0.3, with no modern CMS or analytics detected. The site is served over HTTP/2 but lacks DNSSEC and visible security headers, indicating room for improvement in security hardening. The site is currently protected by a custom automated request detection mechanism that blocks access from VPNs, cloud providers, and suspected automated crawlers, which limits content accessibility and analysis. From a security perspective, the domain registration is stable and trustworthy with no privacy protection, appropriate domain age, and registrar status flags that prevent unauthorized changes. However, the website itself lacks visible security policies, cookie consent mechanisms, and security headers. The blocking mechanism suggests a proactive approach to mitigate automated abuse but also impacts user experience and accessibility. Overall, the website's risk profile is moderate due to limited content accessibility and security best practices. Strategic improvements in security headers, DNSSEC, privacy compliance, and user experience would enhance trust and operational resilience.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
  2. 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';…
  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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 ntldstats.com

This scan found 26 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
65
Security headers
15
Email security
60
DNS health
85
Network security
0
GDPR outside view
53
Average
46

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 · found on this site
  • 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

nTLDStats operates in a niche market providing domain statistics and analytics, serving domain investors and related professionals. The company greenSec GmbH is a small German technology firm with a focused business model on domain data services. The market positioning is specialized with limited direct competition. Revenue streams likely include subscription or data access fees. The partnership ecosystem includes the registrar united-domains GmbH and hosting under greensec.de DNS servers. Growth indicators are not visible due to blocked content. The company maintains a direct contact email for support and incident response but lacks broader marketing or social media presence.

Security posture

The security maturity level is basic with domain registration protections in place but lacking modern DNS security (DNSSEC) and HTTP security headers. The website employs a custom automated request detection mechanism to block suspicious traffic, indicating some level of threat awareness. However, the absence of published security policies, incident response details beyond a contact email, and lack of vulnerability disclosure mechanisms highlight gaps in security culture and compliance. GDPR compliance is unclear due to missing cookie consent and minimal privacy policy details. The blocking of VPN and cloud provider IPs may reduce abuse but also limits legitimate access.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and trust.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies with GDPR compliance and consent mechanisms.
  4. Enhance incident response documentation and provide a dedicated security contact or abuse email.
  5. Review and optimize the automated request detection to reduce false positives and improve user accessibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Automated request detected page blocking access, likely WAF or custom security mechanism blocking VPN, cloud provider IPs, and automated crawlers. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
greenSec GmbH
Description
nTLDStats provides statistical data and insights related to new top-level domains (nTLDs). The business appears to focus on domain statistics and related analytics.
Key services
Domain statistics, Domain analytics, Domain market insights
Content quality
poor
Branding
consistent

Technology

Stack
Bootstrap 3.1.1, Font Awesome 4.0.3, HTTP/2
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
40/100
Good practices seen
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is blocked by automated request detection mechanism
  2. No visible privacy or cookie banners on main page
  3. Contact email provided for access issues
  4. No visible forms or interactive elements on blocked page
  5. Minimal metadata and no Open Graph or JSON-LD structured data found
  6. No social media links detected
  7. No phone numbers or physical addresses found in content
  8. No security headers detected in HTML content
  9. Domain uses DNS servers under greensec.de
  10. No DNSSEC enabled
Technical notes

Notes

The website uses legacy frontend technologies (Bootstrap 3.1.1, Font Awesome 4.0.3) and serves content over HTTP/2. No modern CMS or analytics tools are detected. The hosting provider is not explicitly identified but DNS servers are under greensec.de. Performance and mobile optimization are basic, with minimal accessibility and SEO features. The site lacks structured data, Open Graph tags, and meta descriptions, limiting search engine visibility. The blocking mechanism for automated requests impacts content availability and user experience. Technical debt is indicated by outdated libraries and missing security best practices.
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 ntldstats.com. 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 ntldstats.com.

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.