Skip to main content

Security report for m-g.io

Ampify · Technology · Israel

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

62/100

Risk levelMedium

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

The domain m-g.io is registered to Ampify, an Israeli technology entity founded in 2019. The website content accessible is minimal and primarily consists of an XML listing of files, suggesting it functions as a storage or content bucket rather than a full-fledged website. There is no visible metadata, forms, or user interaction elements, and no privacy or cookie policies are present. The technical infrastructure includes Cloudflare DNS and likely AWS S3 hosting, indicating a modern but basic setup. Security posture is weak due to lack of HTTPS confirmation, security headers, and incident response information. Overall, the site appears legitimate but underdeveloped with limited content and poor user experience.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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. 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. 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';…
  3. 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

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

Keep watching m-g.io

This scan found 25 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
60
DNS health
75
Network security
100
GDPR outside view
50
Average
62

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

Ampify appears to operate in the technology sector, likely providing digital or cloud-based services. The domain age and registration details are consistent with a small technology business. There is no evidence of marketing, advertising, or analytics tools, suggesting a low-profile or internal-facing service. The lack of contact information and policies limits transparency and trust. No partnerships or subsidiaries are identified from the data provided.

Security posture

The security posture is currently weak, with no detected HTTPS enforcement, security headers, or vulnerability disclosure mechanisms. The absence of privacy and cookie policies indicates compliance gaps, particularly regarding GDPR. No incident response contacts or security frameworks are mentioned. The domain uses Cloudflare DNS but does not enable DNSSEC, which could improve DNS security. Overall, the site requires significant improvements to meet modern security and compliance standards.

Recommendations

  1. Implement HTTPS with a valid SSL certificate and enforce secure connections.
  2. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  4. Establish a vulnerability disclosure policy and provide incident response contact information.
  5. Improve website content quality and user experience to enhance trust and professionalism.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ampify
Description
Ampify appears to be the organization behind the domain m-g.io, likely involved in technology services or digital solutions given the domain and hosting context.
Content quality
poor

Technology

Stack
Cloudflare DNS, Amazon S3 (implied by XML namespace)

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 minimal and mostly XML listing of files, indicating a storage or content bucket rather than a full website.
  2. No visible metadata, forms, or user interaction elements found in the provided HTML snippet.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact information or social media links found.
  5. No security headers or advanced security configurations detected.
  6. Domain is registered with a reputable registrar and uses Cloudflare DNS.
  7. No evidence of advertising or analytics scripts.
  8. Content safety is rated safe with no adult or questionable content.
Technical notes

Notes

The website is hosted behind Cloudflare DNS and likely uses AWS S3 for content storage, indicating a cloud-based infrastructure. However, the content is limited to XML file listings without visible HTML metadata, forms, or scripts. No CMS or frameworks are detected. The site lacks performance and accessibility indicators, and no SEO optimizations are evident. Technical modernization and content development are needed to improve functionality and user engagement.
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 m-g.io. 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 m-g.io.

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.