Skip to main content

Security report for 2mountain.com

Other · N/a

Partial score · DNS & email only

34/100

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

The website 2mountain.com is currently under maintenance, displaying only a minimal placeholder message in German indicating that the site will be back shortly. There is no substantive business content, contact information, or policies available on the site. The technical infrastructure is basic, served by an Apache server with mod_pagespeed enabled, but critically lacks a valid SSL/TLS certificate, resulting in no HTTPS support. DNS records are properly configured with A, AAAA, MX, and NS records, but DNSSEC and CAA are not enabled, which could improve security. The absence of privacy, cookie, and terms of service policies indicates non-compliance with GDPR and other privacy regulations. Overall, the site’s security posture is weak due to missing HTTPS and security headers, and the lack of business information reduces trustworthiness.

Scanned

3 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

4 findings rated critical or high. Fix these first.

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

  2. 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
    • 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 2mountain.com

This scan found 8 issues across 4 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
0
Email security
50
DNS health
85
Network security
0
Average
34

Not counted

  • Security headers: did not complete in this scan.
  • GDPR outside view: 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 · 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

Due to the minimal content and lack of business information on the website, it is not possible to determine the company's market position, business model, or target audience. The domain is registered and active with standard DNS and mail configurations, suggesting legitimate ownership. However, the absence of any branding, contact details, or service descriptions limits insights into the company’s operations or competitive advantages. No partnerships or related domains were identified.

Security posture

The security posture of 2mountain.com is poor. The site does not have a valid SSL certificate, serving content only over HTTP, which exposes users to potential interception and data integrity risks. Security headers are minimal, and no advanced protections such as HSTS, DNSSEC, or OCSP stapling are implemented. There are no indications of vulnerability scanning or mitigation mechanisms. The lack of privacy and cookie policies further indicates compliance gaps. Incident response and vulnerability disclosure mechanisms are not present, reducing the site's readiness to handle security incidents.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS and protect user data.
  2. Implement essential security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish privacy and cookie policies to comply with GDPR and inform users about data handling.
  4. Add clear contact information and business details to improve trust and credibility.
  5. Enable DNSSEC and CAA records to enhance DNS security and certificate issuance control.
Technical notes

Notes

The website is hosted on an Apache server with mod_pagespeed enabled, indicating some optimization efforts. However, the lack of HTTPS and minimal content result in poor performance and user experience. No CMS or frameworks are detected, and no analytics or tracking technologies are present. The site’s DNS configuration is standard but lacks advanced security features. The overall technical implementation is basic and requires modernization and security enhancements to meet current web standards.
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 2mountain.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 2mountain.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.