Skip to main content

Security report for moneureden.com

Other · N/a

Medium risk. 9 critical or high findings in DNS health, Security headers and 3 other checks.

Security score

60/100

Risk levelMedium

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

The analyzed domain auth.ddfbackend.com is inaccessible, returning a 403 Forbidden error page with minimal HTML content. No metadata, scripts, forms, or business information are available, indicating the site is either restricted or not publicly accessible. The WHOIS lookup failed to find any registration data for the domain, suggesting it may be an internal subdomain or unregistered, which raises legitimacy concerns. Due to the lack of accessible content and registration data, a comprehensive business or security analysis is not feasible. From a technical perspective, the site lacks any detectable technologies, frameworks, or hosting information. The absence of security headers and SSL configuration details further limits the security posture assessment. No privacy, cookie, or terms of service policies are present, indicating non-compliance with common privacy regulations. The site does not provide any contact or incident response information. Overall, the security posture is poor due to the lack of accessible content and security best practices. The domain's legitimacy is questionable given the missing WHOIS data and blocked access. Strategic recommendations include enabling proper public access, implementing HTTPS with security headers, publishing privacy and cookie policies, and ensuring WHOIS registration data is accurate and publicly available to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 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. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • Critical

      DNS Resolution Failed

      Unable to resolve domain A records

      What to do: Verify domain is properly configured and not expired

  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 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

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

Keep watching moneureden.com

This scan found 24 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
77
Security headers
15
Email security
90
DNS health
40
Network security
100
GDPR outside view
40
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

Due to the absence of accessible website content and WHOIS registration data, no meaningful business intelligence can be derived. The domain appears to be a backend authentication endpoint, likely used internally or as part of a private API infrastructure rather than a public-facing business website. No information about market positioning, business model, or partnerships is available.

Security posture

The security posture is currently very weak. The site is inaccessible with a 403 Forbidden error, which may be intentional for security but prevents analysis of security headers, SSL configuration, or vulnerability exposure. No privacy or security policies are published, and no incident response contacts are available. The missing WHOIS data further complicates trust assessment. The site should implement HTTPS, security headers, and publish compliance documentation to improve its security maturity.

Recommendations

  1. Enable HTTPS with a valid SSL/TLS certificate to secure communications.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish privacy, cookie, and terms of service policies to comply with GDPR and other regulations.
  4. Ensure WHOIS registration data is complete and publicly accessible to improve domain legitimacy.
  5. Provide accessible contact and incident response information to support security and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. The website returns a 403 Forbidden error with minimal HTML content, indicating access is blocked or restricted. No specific WAF vendor detected. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

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
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No metadata, scripts, forms, or external links found in the HTML.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact information or business details available.
  5. No security headers or SSL information available from provided data.
  6. Domain WHOIS data is missing, indicating possible non-public registration or internal use.
  7. Website is effectively blocked from public access, limiting analysis.
Technical notes

Notes

The website currently serves only a 403 Forbidden error with no additional HTML content, metadata, or scripts. No CMS, frameworks, or hosting provider information is detectable. The lack of accessible content and technical details suggests the site is either restricted for security reasons or not intended for public access. Performance, mobile optimization, and SEO cannot be assessed. Technical modernization and transparency are recommended.
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 moneureden.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 moneureden.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.