Skip to main content

Security report for plaka.com.mx

Other · N/a

Medium risk. 8 critical or high findings in Email security, SSL/TLS and 2 other checks.

Security score

60/100

Risk levelMedium

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

The website www.plaka.com.mx is currently inaccessible due to a Cloudflare Web Application Firewall (WAF) challenge page that requires browser verification before granting access. This security measure blocks automated access and obscures the actual website content, preventing a full analysis of the business, services, and compliance posture. The domain WHOIS data is unavailable or invalid, which raises concerns about the transparency and legitimacy of the domain registration. The site uses Google Tag Manager for analytics and Cloudflare Turnstile captcha for bot mitigation, indicating some level of security awareness. However, the lack of visible privacy policies, contact information, and business details on the landing page limits trust and credibility assessment. Overall, the site appears to be protected by strong security controls but lacks accessible content for evaluation.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 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

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.

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

  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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

  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 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';…

  4. 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 plaka.com.mx

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
52
Security headers
70
Email security
40
DNS health
65
Network security
100
GDPR outside view
35
Average
60

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

Due to the WAF challenge, no direct business information, company name, or sector details are available. The domain appears to be small in size with no visible market positioning or business model information. The use of Google Tag Manager suggests some marketing and analytics efforts, but no partner or subsidiary domains were identified. The absence of contact details and policies indicates a low level of transparency and customer engagement on the publicly accessible page.

Security posture

The website employs Cloudflare's WAF and Turnstile captcha, which are effective for mitigating automated threats and DDoS attacks. However, no security headers were detected in the provided data, and the SSL/TLS configuration could not be assessed. The lack of visible privacy and cookie policies, as well as absence of contact channels for incident response, suggests gaps in compliance and security communication. The domain's WHOIS data is missing, which is a negative indicator for trustworthiness. Overall, the security posture is mixed: strong perimeter defense but poor transparency and compliance visibility.

Recommendations

  1. Work with hosting and DNS providers to allow safe access for security and compliance audits by trusted parties.
  2. Publish clear and comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  3. Add visible business contact information including emails and phone numbers to improve trust and customer support.
  4. Implement and expose security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  5. Ensure WHOIS data is complete and accurate to enhance domain legitimacy and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Website is behind Cloudflare WAF with a browser challenge page including Turnstile captcha and 'We're checking your browser before allowing access.' message. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
Google Tag Manager, Cloudflare Turnstile Captcha

Security

Observed score
25/100
Good practices seen
  • Use of Cloudflare WAF and Turnstile captcha for bot mitigation

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
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 Cloudflare WAF challenge
  2. No visible business or contact information on the landing page
  3. No privacy, cookie, or terms of service policies detected
  4. No forms or data collection fields visible except hidden captcha response input
  5. Use of Google Tag Manager for analytics and tracking
  6. No WHOIS data available to verify domain registration details
  7. Website likely uses Cloudflare for DDoS protection and bot mitigation
Technical notes

Notes

The website uses Google Tag Manager for analytics and Cloudflare services for security and performance. The HTML content is minimal and serves only as a browser challenge page, indicating the site is protected by a managed security service. No CMS or backend technologies could be identified. The site lacks SEO metadata, structured data, or accessible content, which negatively impacts discoverability and user experience. Performance and mobile optimization cannot be assessed due to the blocking page. The obfuscated JavaScript is used for bot detection and cookie management. Overall, the technical infrastructure prioritizes security over accessibility.
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 plaka.com.mx. 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 plaka.com.mx.

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.