Skip to main content

Security report for mercos.com

Mercos · E-commerce · Brazil

Medium risk. 7 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

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

Mercos is a Brazilian software company specializing in B2B sales automation and e-commerce solutions tailored for industries, distributors, and commercial representatives. Positioned as one of the most utilized sales systems in the market, Mercos offers a comprehensive suite of services including sales force automation, B2B e-commerce portals, AI-powered order processing, payment systems, and video call sales features. The company targets medium-sized businesses seeking to streamline their sales operations and integrate seamlessly with existing ERP systems. Their market presence is reinforced by over 8,700 clients and 52,000 users, highlighting strong adoption and trust within their niche. Technically, Mercos leverages modern web technologies such as React and JavaScript, hosted on Amazon Web Services infrastructure with CloudFront CDN for content delivery. The site integrates multiple marketing and analytics tools including Google Tag Manager, HubSpot, RD Station, and Visual Website Optimizer, indicating a mature digital marketing strategy. Performance is optimized with preloading scripts and responsive design, ensuring good mobile experience and SEO. From a security perspective, Mercos maintains a valid SSL certificate issued by Amazon but currently lacks support for modern TLS protocols and advanced security headers. DNS security features like DNSSEC and CAA are not enabled, and no explicit security or incident response policies are publicly disclosed. While no critical vulnerabilities are detected, the absence of cookie consent mechanisms and limited privacy compliance features suggest areas for improvement. Overall, Mercos presents a robust business and technical foundation with excellent user experience and market positioning. However, enhancing security configurations, privacy compliance, and transparency around incident response would strengthen their risk posture and customer trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

7 findings rated critical or high. Fix these first.

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

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

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

Keep watching mercos.com

This scan found 17 issues across 5 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
85
Security headers
15
Email security
100
DNS health
85
Network security
100
GDPR outside view
25
Average
68

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention mercos.com, from OffSeq Breach.

Total records
9,363
Employees
4
Customers
9,332
Third parties
27
Weak passwords
43%

Latest record dated 2025-07-28 · 274 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for mercos.com.

Select it in the checkout above.

Masked preview

  • –sandbox.mercos.com2025-07-28
  • –dados.mercos.com2025-07-28
  • –app.mercos.com2025-07-28
  • –app.mercos.com2025-07-20

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Mercos operates in the B2B software market focusing on sales automation and e-commerce for industries, distributors, and representatives. Their competitive advantage lies in deep ERP integration, AI-enhanced order processing, and a comprehensive product suite addressing multiple sales channels. Revenue streams likely include subscription fees for SaaS offerings and transaction fees via Mercos Pay. The company targets medium-sized enterprises in Brazil, leveraging a strong partner ecosystem including ERP providers and marketing platforms. Growth indicators include a large user base and extensive ERP integrations. Strategic observations highlight Mercos' emphasis on customer success through demos, trials, and support, as well as a diversified marketing approach using multiple digital tools.

Security posture

Mercos demonstrates a moderate security maturity level with a valid SSL certificate and absence of known SSL vulnerabilities. However, the lack of TLS 1.2+ support, missing security headers, and no DNSSEC implementation indicate gaps in foundational security controls. The absence of a published security policy, incident response plan, or vulnerability disclosure program limits transparency and preparedness for security incidents. Privacy compliance is basic, with a privacy policy present but no cookie consent mechanism despite active tracking scripts. These gaps could expose the company to regulatory risks and reduce customer confidence. Business impact includes potential data privacy concerns and increased risk of exploitation through outdated protocols. Enhancing security posture with modern TLS, security headers, DNSSEC, and clear incident response procedures is recommended.

Recommendations

  1. Enable TLS 1.2 or higher protocols to secure data in transit and improve compatibility.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to mitigate common web attacks.
  3. Deploy DNSSEC and configure CAA records to enhance domain name system security and certificate issuance control.
  4. Publish a comprehensive security policy and incident response plan, including contact channels for vulnerability reporting.
  5. Introduce a cookie consent mechanism to comply with privacy regulations and improve transparency with users.

Contact details published on the site

Addresses
Legal name
Simplest Software Ltda
Technical notes

Notes

Mercos utilizes a modern technology stack centered on React and JavaScript, hosted on AWS infrastructure with CloudFront CDN for efficient content delivery. The site is optimized for performance with script preloading and responsive design, delivering a fast and mobile-friendly user experience. Integration with multiple marketing and analytics platforms indicates a mature digital marketing approach. However, the absence of a detected CMS suggests a custom or headless architecture. Technical risks include outdated TLS protocol support and lack of advanced security headers, which could impact secure operations. Opportunities exist to modernize security configurations and enhance accessibility features to further improve technical robustness.
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 mercos.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 mercos.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.