Skip to main content

Security report for carte.bio

Technology · N/a

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

50/100

Risk levelMedium

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

GoGoCarto is a French-language web platform designed to enable users to create and share map projects easily. It targets a general audience interested in mapping and geographic data visualization, offering open source code access and documentation to support user engagement. The platform positions itself as a niche technology tool with a focus on community-driven map creation. Technically, the website employs standard web technologies including HTML5, CSS3, JavaScript, and FontAwesome icons, with moderate performance and good mobile responsiveness. However, the site lacks advanced frameworks or CMS detection and does not show evidence of strong hosting or performance optimization. From a security perspective, the site currently exhibits minimal security posture with no detected security headers or explicit HTTPS confirmation in the provided data. There are no visible privacy or cookie policies, nor contact or incident response information, which limits compliance and transparency. The WHOIS data is privacy protected or unavailable, which is common for small projects but reduces trust signals. Overall, the site is safe for general audiences and provides a functional, well-branded user experience but would benefit from enhanced security and compliance measures.

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching carte.bio

This scan found 24 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. 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
62
Security headers
25
Email security
70
DNS health
75
Network security
20
GDPR outside view
50
Average
50

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

The business model centers on providing a platform for user-generated map projects, supported by open source code and documentation. The target market includes individuals and organizations interested in geographic data visualization and mapping tools. The platform's competitive advantage lies in its ease of use and open source nature, appealing to a community of contributors and users. Revenue streams are not explicit from the analyzed content, suggesting a possible community or nonprofit orientation. The partnership ecosystem includes links to documentation and a GitLab repository hosted by Adullact, indicating collaboration with open source communities. Growth indicators are limited due to lack of public business data. Strategic observations highlight the need for improved transparency and security to enhance trust and adoption.

Security posture

The current security maturity level is low, with no detected security headers or HTTPS confirmation in the provided data. The absence of privacy and cookie policies indicates compliance gaps with GDPR and other data protection regulations. No incident response or security contact information is available, limiting readiness for security events. Data protection practices are unclear due to lack of visible policies or disclosures. The security culture appears minimal, with no visible trust indicators such as certifications or security badges. The platform should prioritize implementing HTTPS, security headers, and comprehensive privacy documentation to improve its security posture and compliance.

Recommendations

  1. Implement HTTPS with a strong SSL/TLS configuration to secure all communications.
  2. Add standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish clear and comprehensive privacy and cookie policies to comply with GDPR and enhance user trust.
  4. Provide visible contact information including security and incident response contacts.
  5. Conduct a security audit of all forms and scripts to identify and remediate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
GoGoCarto is a platform to create maps easily ('Créez des cartes à GoGo').
Key services
Map creation, Project hosting, Documentation and source code access
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, FontAwesome 5, List.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is a French-language platform for creating and sharing map projects.
  2. No WHOIS registrant details publicly available; domain uses privacy protection or unsupported TLD WHOIS.
  3. No privacy, cookie, or terms of service policies found on the analyzed page.
  4. No contact emails, phone numbers, or social media links found on the page.
  5. No security headers or explicit HTTPS confirmation from provided data; security posture is minimal.
  6. No advertising or tracking technologies detected.
  7. Website content is safe and appropriate for general audiences.
  8. Technical implementation uses standard web technologies with moderate performance and good mobile optimization.
  9. No forms with personal data collection detected on the analyzed page.
  10. External links point to documentation and source code repositories related to the project.
Technical notes

Notes

The website uses a straightforward technology stack with HTML5, CSS3, JavaScript, and FontAwesome icons. It includes the List.js library for client-side list management. The site is mobile optimized with responsive design and uses meta tags for viewport and mobile web app capabilities. Performance is moderate with no explicit optimization indicators. There is no detected CMS or advanced framework. Hosting provider details are not available. The site lacks advanced accessibility features and SEO optimizations are basic. Technical risks include potential lack of HTTPS and missing security headers, which could expose users to risks. Modernization opportunities include adopting a CMS or framework for better scalability and integrating security best practices.
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 carte.bio. 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 carte.bio.

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.