Skip to main content

Security report for server-m2m.com

Other · N/a

High risk. 10 critical or high findings in Email security, Network security and 3 other checks.

Security score

45/100

Risk levelHigh

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

The website server-m2m.com presents a minimal online presence with only a basic welcome message and meta description. The lack of substantive content, contact information, and policy pages indicates a very early or placeholder stage of development. The domain is registered since 2017 with a reputable registrar and shows no signs of suspicious activity, suggesting legitimacy but limited business maturity or online engagement. Technically, the site lacks modern web technologies, security headers, and SEO optimizations, resulting in a low digital maturity score. Security posture is weak due to absence of security headers and DNSSEC, though HTTPS is presumably enabled given the domain status and no explicit issues. Overall, the site poses low risk but also low trust and credibility due to minimal content and lack of transparency.

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

10 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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

  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 server-m2m.com

This scan found 28 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
72
Security headers
15
Email security
75
DNS health
70
Network security
0
GDPR outside view
40
Average
45

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

The business behind server-m2m.com appears to be small and possibly in early stages or inactive online, given the minimal content and lack of business details. No clear market positioning, services, or target audience can be identified from the site. The domain age aligns with a business founded in 2017, but no growth indicators or partnerships are visible. The absence of contact details and policies limits customer engagement and trust. There is no evidence of revenue streams or competitive advantages from the website alone.

Security posture

Security maturity is low with no published security policies, incident response contacts, or vulnerability disclosures. The domain uses clientTransferProhibited status which is positive, but DNSSEC is not enabled. No security headers are detected, and no advanced security frameworks or certifications are mentioned. The site does not collect user data or have forms, reducing attack surface but also limiting functionality. Compliance with GDPR or other regulations cannot be confirmed due to missing policies. Incident response readiness appears absent.

Recommendations

  1. Publish comprehensive privacy, cookie, and terms of service policies to improve compliance and user trust.
  2. Add clear contact information including emails and phone numbers for customer and security incident communication.
  3. Implement security headers (CSP, HSTS, X-Frame-Options) and enable DNSSEC to strengthen domain and site security.
  4. Enhance website content with relevant business information and improve design and navigation for better user experience.
  5. Consider adding vulnerability disclosure and incident response information to demonstrate security maturity.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Ths is an Index.html file
Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
30/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 content is extremely minimal, consisting only of a basic welcome message and meta description.
  2. No privacy, cookie, or terms of service policies are present.
  3. No contact information or forms are available on the site.
  4. No external links, social media, or scripts detected.
  5. No security headers or advanced security configurations detected.
  6. Domain registration is stable and consistent with business age.
  7. No analytics or advertising technologies detected.
  8. Website lacks SEO and accessibility optimizations.
  9. No evidence of adult or questionable content.
Technical notes

Notes

The website is built with basic HTML without any detected CMS, frameworks, or external scripts. No analytics or marketing tools are present. The site performance is likely moderate due to minimal content but lacks mobile optimization and accessibility features. SEO is poor with only a basic meta description and no structured data or Open Graph tags. Hosting provider and platform details are not discernible from the content. The domain uses name servers dns1.orbis.hr and dns2.orbis.hr, but no DNSSEC is enabled. Overall, the technical infrastructure is minimal and could benefit from modernization and security enhancements.
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 server-m2m.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 server-m2m.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.