Skip to main content

Security report for mansagaming.com

Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

48/100

Risk levelHigh

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

The website mansagaming.com currently presents an extremely minimal online presence, displaying only the domain name text without any additional content, metadata, or interactive elements. This lack of substantive content and absence of business information makes it difficult to ascertain the company's market position, services, or target audience. The site appears to be either a placeholder or under construction, lacking essential elements such as privacy policies, contact details, or security features. From a technical perspective, the website does not utilize any detectable technologies, frameworks, or content management systems. There is no evidence of HTTPS encryption or security headers, which are critical for protecting user data and establishing trust. The site also lacks SEO optimization, accessibility features, and mobile responsiveness, indicating a low level of digital maturity. Security posture is weak due to the absence of HTTPS and security best practices. No privacy or cookie policies are present, and no contact or incident response information is available. These gaps pose compliance risks and reduce user trust. Overall, the website's current state represents a high-risk profile with significant vulnerabilities and compliance deficiencies. Strategically, the business should prioritize establishing a secure, content-rich website with clear policies and contact information to improve credibility and compliance. Implementing HTTPS and security headers is essential to protect visitors and enhance trust. Developing comprehensive privacy and cookie policies aligned with GDPR and other regulations will mitigate legal risks. Enhancing technical infrastructure and content quality will support better user experience and market positioning.

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

8 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. 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';…

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

Keep watching mansagaming.com

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
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
15
Average
48

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 lack of content and business information on the website, it is not possible to perform a detailed business intelligence analysis. No information about market positioning, competitive advantages, revenue streams, or partnerships is available. The absence of contact details and company data suggests the business is either very early stage or inactive online. No indicators of growth or strategic direction can be identified from the current website.

Security posture

The website demonstrates a very low security maturity level. The absence of HTTPS means data transmitted to and from the site is not encrypted, exposing users to interception risks. No security headers are present to mitigate common web vulnerabilities. There is no evidence of vulnerability disclosure or incident response mechanisms, indicating a lack of preparedness for security incidents. Compliance with data protection regulations such as GDPR is unlikely given the missing privacy and cookie policies. Overall, the security posture is inadequate for any business handling user data or transactions.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure all website traffic.
  2. Add standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Develop and publish comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  4. Include clear contact information and business details to improve transparency and trust.
  5. Enhance website content, structure, and technical implementation to improve user experience, SEO, and accessibility.
Site observations

Automated reading of the public site. Ratings are indicative.

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 extremely minimal, consisting only of the domain name text
  2. No metadata, no structured data, no forms, no external links, no contact information
  3. No scripts or technologies detected in the HTML content
  4. No security headers or SSL information available
  5. No privacy, cookie, or terms of service policies found
  6. No business or legal information present on the site
  7. Website appears to be a placeholder or under construction
Technical notes

Notes

The website's technical implementation is minimal and lacks modern web development practices. The HTML is basic with no metadata, scripts, or linked resources. There is no detectable CMS or framework. Performance and mobile optimization cannot be properly assessed due to lack of content. The absence of HTTPS and security headers represents a critical technical risk. The site requires modernization to meet current web standards and security expectations.
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 mansagaming.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 mansagaming.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.