Skip to main content

Security report for mcmath.info

Other · N/a

High risk. 10 critical or high findings in Network security, SSL/TLS and 2 other checks.

Security score

45/100

Risk levelHigh

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

The website www.mcmath.info is currently inaccessible to visitors, presenting a 403 Forbidden error page that indicates permission or access control restrictions. The page content is limited to technical explanations about 403 errors and guidance on file permissions and .htaccess modifications, with no business or contact information available. The lack of accessible content and absence of privacy, cookie, or terms of service policies suggest the site is either under maintenance, misconfigured, or restricted. Technically, the site loads jQuery 3.3.1 but lacks modern security headers or visible HTTPS enforcement, which raises concerns about its security posture. WHOIS data is unavailable due to a malformed query response, preventing verification of domain registration details and reducing trust in the domain's legitimacy. Overall, the site exhibits poor content quality, minimal technical sophistication, and weak security and privacy compliance.

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

10 findings rated critical or high. Fix these first.

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

  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. 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 mcmath.info

This scan found 27 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
47
Security headers
15
Email security
85
DNS health
75
Network security
0
GDPR outside view
50
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

Due to the absence of accessible business content, no meaningful business intelligence can be derived. There is no indication of company name, services, market positioning, or target audience. The domain appears to be small scale or personal, with no visible partnerships or certifications. The lack of contact information and policies further limits assessment of business credibility or operational maturity.

Security posture

The security posture is weak, primarily due to the 403 Forbidden error indicating access restrictions likely caused by misconfigured permissions or IP deny rules. No security headers or HTTPS status are evident, and no incident response or vulnerability disclosure information is present. The site does not demonstrate adherence to security best practices or compliance frameworks. The absence of WHOIS data and registrant information further complicates trust evaluation. Immediate remediation should focus on correcting server permissions, enabling HTTPS, and implementing standard security headers.

Recommendations

  1. Review and correct file and directory permissions to ensure proper access rights (644 for files, 755 for directories).
  2. Audit and adjust .htaccess rules to remove conflicting IP deny directives that may block legitimate users.
  3. Implement HTTPS with a valid SSL/TLS certificate to secure data in transit and improve trust.
  4. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Publish clear privacy, cookie, and terms of service policies to enhance compliance and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. The website returns a 403 Forbidden error page indicating access is blocked due to permission or IP deny rules. No specific WAF vendor branding detected. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
jQuery 3.3.1
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 inaccessible due to 403 Forbidden error
  2. No business or contact information is present on the page
  3. No privacy, cookie, or terms of service policies found
  4. Minimal technical footprint detected (only jQuery 3.3.1 loaded externally)
  5. No security headers or HTTPS status information available
  6. WHOIS data is unavailable or blocked, limiting domain trust assessment
Technical notes

Notes

The website uses jQuery 3.3.1 loaded from an external CDN but lacks other detectable modern technologies or CMS platforms. The HTML content is minimal and static, serving only an error message. There is no evidence of SEO optimization, mobile responsiveness, or accessibility features. Hosting provider and SSL configuration details are not discernible from the content. The site performance is likely moderate given the minimal content but user experience is poor due to access denial. Technical debt is implied by the lack of proper configuration and missing security controls.
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 mcmath.info. 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 mcmath.info.

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.