Skip to main content

Security report for mvpxo.com

Other · N/a

Partial score · DNS & email only

55/100

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

The website mvpxo.com is currently non-functional, displaying a Discuz! database connection error page with detailed debug information exposed. There is no accessible business content, contact information, or privacy and cookie policies. The WHOIS data shows inconsistencies, notably a domain creation date set in the future (February 2025), which undermines trust and legitimacy. The technical infrastructure is based on PHP and Discuz! CMS, hosted via DNSPod, Inc., but the site suffers from critical backend failures and lacks modern security configurations such as DNSSEC and security headers. Overall, the site exhibits poor content quality, minimal technical implementation, and weak security posture, resulting in a low trust and credibility score.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
6of 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

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

    • 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

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

  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.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • 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

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

Keep watching mvpxo.com

This scan found 18 issues across 5 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
62
Email security
70
DNS health
75
Network security
20
GDPR outside view
50
Average
55

Not counted

  • Security headers: did not complete in this scan.
  • 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 accessible content and business information, no meaningful business intelligence can be derived. The absence of contact details, company name, or service descriptions prevents assessment of market positioning, business model, or target audience. The domain's suspicious WHOIS data further complicates trust in the business operations. No partnerships or related domains are identified.

Security posture

The security posture is weak, with no evidence of HTTPS enforcement or security headers. The exposure of detailed database error messages publicly is a significant vulnerability, potentially aiding attackers. DNSSEC is not enabled, and the domain WHOIS data lacks transparency. There is no indication of incident response policies or vulnerability disclosure mechanisms. The site is vulnerable to downtime and information leakage, requiring urgent remediation.

Recommendations

  1. Restore database connectivity and ensure backend stability to bring the website online.
  2. Remove or restrict detailed error/debug information from public-facing pages to prevent information leakage.
  3. Implement HTTPS with a valid SSL certificate and enforce secure connections site-wide.
  4. Enable DNSSEC on the domain to improve DNS security and trustworthiness.
  5. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  6. Publish clear privacy, cookie, and terms of service policies to improve compliance and user trust.
  7. Provide verifiable contact information and business details to enhance credibility.
  8. Review and correct WHOIS data to reflect accurate domain registration information.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
PHP, MySQL (mysqli)
Frameworks
Discuz!
Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
20/100

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 is currently non-functional showing a Discuz! database connection error
  2. No visible privacy, cookie, or terms of service policies
  3. No contact information or business details available on the page
  4. No security headers or HTTPS status visible from provided data
  5. WHOIS data contains suspicious future creation date
  6. No analytics or advertising scripts detected
  7. No social media or external business links except references to official Discuz! and ICANN sites
  8. Content is minimal and purely error message with debug trace
  9. No forms or data collection elements present
  10. No evidence of adult or unsafe content
Technical notes

Notes

The website runs on PHP with the Discuz! CMS framework and uses MySQL via the mysqli driver. The hosting provider is DNSPod, Inc. The site currently fails to connect to its database, resulting in a full outage and display of raw error messages. There is no evidence of modern frontend technologies or performance optimizations. The site lacks mobile optimization and accessibility features. SEO is minimal due to the absence of meta tags beyond basic charset and viewport. The domain's DNS configuration lacks DNSSEC, and no security headers are detected. Overall, the technical implementation is outdated and requires modernization and hardening.
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 mvpxo.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 mvpxo.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.