Skip to main content

Security report for inaut.net

easyname GmbH · Other · Germany

High risk. 11 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

29/100

Risk levelHigh

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

The website inaut.net is currently a parked domain managed by easyname GmbH, a domain parking and management service provider based in Germany. The site contains no active business content, serving only as a placeholder with links to easyname's main website and control panel for domain owners. The target audience is domain owners or potential buyers, and the business model revolves around domain parking services. The site is minimalistic with basic design and limited user engagement features. From a technical perspective, the site is hosted on an Apache server with no SSL/TLS certificate installed, resulting in HTTP-only access. The performance metrics indicate no measurable load time or resources, consistent with a simple parked page. The site lacks modern web technologies, frameworks, or CMS platforms and shows only basic mobile optimization and accessibility features. Security posture is weak due to the absence of HTTPS, lack of security headers beyond a minimal permissions policy, and no evidence of vulnerability management or incident response policies. The domain's WHOIS data is consistent with the parking service provider, showing no suspicious patterns or privacy protection. However, the lack of SSL/TLS and security best practices poses risks if the domain were to be used actively. Overall, the site scores low on content quality, technical implementation, security, privacy compliance, and business credibility due to its nature as a parked domain. Strategic recommendations include enabling HTTPS with a valid certificate, implementing comprehensive security headers, adding privacy and cookie policies if the domain becomes active, and improving content and user engagement to enhance trust and professionalism.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

11 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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
    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL 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
  4. 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

Need hands-on remediation? Email guard@offseq.com

Keep watching inaut.net

This scan found 20 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
0
Security headers
25
Email security
50
DNS health
85
Network security
0
GDPR outside view
15
Average
29

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

The domain inaut.net is currently not used for active business operations but is parked by easyname GmbH, a small German company specializing in domain parking and management services. The business model is straightforward, providing domain owners with parking services and control panel access. There is no direct revenue generation from this domain itself. The market position is limited to domain parking, with no competitive business content or services offered. The partnership ecosystem is limited to easyname's own infrastructure. No growth indicators or strategic partnerships are evident from the domain content or WHOIS data.

Security posture

The security maturity of the website is minimal. The absence of HTTPS is a critical vulnerability, exposing users to potential interception and man-in-the-middle attacks. No advanced security headers or mechanisms such as HSTS, CSP, or OCSP stapling are implemented. There is no evidence of incident response readiness or published security policies. The domain does not collect user data or have forms, reducing immediate risk, but the lack of encryption and security best practices is a significant concern if the domain were to be repurposed. Compliance with GDPR or other regulations is not demonstrated due to missing privacy and cookie policies.

Recommendations

  1. Enable HTTPS with a valid SSL/TLS certificate immediately to secure communications.
  2. Implement comprehensive security headers including HSTS, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish privacy and cookie policies if the domain is to be used for active services or data collection.
  4. Establish incident response contact channels and security policies to improve trustworthiness.
  5. Enhance website content and user engagement to improve business credibility and SEO.
Technical notes

Notes

The website is hosted on an Apache server with no SSL/TLS enabled, serving only a static HTML page for domain parking. No CMS or advanced frameworks are detected. The site lacks performance optimization and modern web technologies. Mobile optimization and accessibility are basic, with minimal styling and no interactive elements. The DNS configuration is standard with no DNSSEC or CAA records enabled. The domain uses easyname's nameservers and mail exchange services via Outlook protection. Overall, the technical infrastructure is minimal and suitable only for domain parking, with significant modernization needed for active business use.
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 inaut.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 inaut.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.