Skip to main content

Security report for metacure.com

Other · N/a

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

Security score

42/100

Risk levelHigh

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

The website metacure.com currently serves only a minimal HTML page that immediately redirects visitors to a /lander path, with no visible content, metadata, or business information. The domain is registered and resolves to IP addresses likely hosted on Amazon AWS, but lacks a valid SSL certificate and does not support HTTPS, exposing visitors to security risks. No privacy, cookie, or terms of service policies are present, and no contact or company information is available on the site. The technical infrastructure is minimal and lacks modern security and performance optimizations, resulting in a poor user experience and low trustworthiness. From a security perspective, the absence of HTTPS and security headers, combined with no DNSSEC or CAA records, indicates a weak security posture. The domain's DNS configuration is incomplete, with no valid MX records, which may affect email deliverability and trust. No analytics or tracking technologies are detected, suggesting minimal digital maturity. Overall, the site appears to be either under development, abandoned, or a placeholder with no active business presence. Given these findings, the overall risk level is high due to lack of encryption, absence of policies, and no verifiable business identity. Strategic recommendations include obtaining and configuring a valid SSL certificate, implementing security best practices such as HSTS and security headers, publishing privacy and cookie policies to comply with regulations, and providing clear contact and business information to improve credibility and trust.

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

9 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 metacure.com

This scan found 19 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
15
Email security
50
DNS health
70
Network security
100
GDPR outside view
15
Average
42

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, no meaningful business intelligence can be derived. The domain is registered and hosted on AWS infrastructure, but no company name, description, services, or market positioning is disclosed. There are no visible partnerships, certifications, or trust signals. The absence of MX records and contact details further limits the ability to assess the business model or target audience. This suggests the domain may be inactive, a placeholder, or under early development without public-facing business operations.

Security posture

The security posture of metacure.com is weak. The site does not have a valid SSL certificate and does not support HTTPS, exposing users to potential interception and data tampering. No security headers such as Content-Security-Policy or X-Frame-Options are present, and DNSSEC is not enabled, increasing the risk of DNS spoofing. The absence of MX records and security policies further reduces trust. No known vulnerabilities such as Heartbleed or POODLE are detected, but the lack of basic security controls is a critical issue. Incident response and vulnerability disclosure mechanisms are not found, indicating low security maturity and readiness.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the site immediately.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Configure DNSSEC and CAA records to enhance DNS security and certificate issuance control.
  4. Add essential security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Publish comprehensive privacy, cookie, and terms of service policies to comply with GDPR and other regulations.
  6. Provide clear and verifiable contact information and business details to improve trust and credibility.
  7. Configure proper MX records for reliable email communication and domain reputation.
  8. Implement a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  9. Enhance website content with meaningful information, metadata, and SEO optimizations.
  10. Consider adding analytics and monitoring tools to improve digital maturity and user insights.
Technical notes

Notes

The website is hosted on IP addresses associated with Amazon AWS but lacks a valid SSL certificate and does not support any TLS protocols. The HTTP response headers are minimal and do not include security or caching headers. DNS records show multiple A records but no AAAA or properly configured MX records. No CMS, frameworks, or third-party libraries are detected from the HTML content, which consists solely of a redirect script. Performance metrics are zero, indicating no measurable content load. The site is not mobile optimized and lacks accessibility and SEO features. Overall, the technical implementation is minimal and outdated, with significant modernization opportunities to improve security, performance, and user experience.
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 metacure.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 metacure.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.