Skip to main content

Security report for gob.mx

Gobierno de México · Government · Mexico

Medium risk. 9 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

58/100

Risk levelMedium

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

Gob.mx is the official digital portal of the Mexican federal government, providing citizens with access to federal procedures, social programs, and government services. It serves as a centralized platform to facilitate government-citizen interactions, offering key services such as procedure lookup, social program information, and secure authentication via LLave MX. The portal targets Mexican citizens and residents seeking government services online, positioning itself as the authoritative government digital gateway. Technically, the website employs modern web technologies including JavaServer Faces with PrimeFaces, jQuery, and Swiper.js for UI components. It leverages Google Fonts and Google Tag Manager for typography and analytics respectively. Hosting appears to be supported by Akamai CDN, ensuring performance and availability. The site is mobile optimized with responsive design and basic accessibility features. From a security perspective, the site uses HTTPS with strong SSL configuration and includes several security headers. However, it lacks explicit cookie consent mechanisms and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the HTML content. The domain WHOIS data confirms the site is legitimately registered to the Mexican government, reinforcing trust. Overall, gob.mx demonstrates a mature digital government presence with good technical and security posture. To enhance compliance and user trust, it should implement explicit cookie consent, publish security and privacy policies more prominently, and provide clear contact information for data protection and incident response.

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

9 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 gob.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. 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
47
Security headers
20
Email security
70
DNS health
75
Network security
100
GDPR outside view
35
Average
58

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

Gob.mx holds a strong market position as the sole official federal government portal for digital services in Mexico. Its business model is service-oriented, focusing on providing digital access to government procedures and social programs. The portal's competitive advantage lies in its official status, comprehensive service catalog, and integration with government identity systems like LLave MX. Revenue streams are not applicable as it is a government service. Target customers are Mexican citizens and residents requiring government services. The portal shows growth potential through planned integration of state and municipal services. Its partnership ecosystem includes various government agencies and transparency platforms, enhancing service breadth and trust.

Security posture

The security maturity of gob.mx is solid with HTTPS enforcement, secure cookie settings, and use of security headers. The absence of exposed sensitive data and use of reputable hosting/CDN providers further strengthen security. However, gaps exist in privacy compliance such as missing cookie consent and lack of published incident response contacts. No vulnerability disclosure mechanism or security.txt file was found, which could hinder coordinated vulnerability reporting. The site shows readiness for incident response but lacks explicit public documentation. Overall, the security posture is good but can be improved by formalizing policies and transparency.

Recommendations

  1. Implement a visible cookie consent banner to comply with GDPR and other privacy regulations.
  2. Publish a dedicated security policy and incident response contact information on the website.
  3. Create and host a security.txt file to facilitate vulnerability disclosure and improve transparency.
  4. Enhance accessibility features to meet recognized standards and improve user inclusivity.
  5. Add clear contact information for the Data Protection Officer and general inquiries to improve trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Gobierno de México
Description
El portal gob.mx permite consultar el listado de trámites y programas sociales federales disponibles y a los cuales tienes acceso.
Key services
Consulta de trámites federales, Acceso a programas sociales, Creación de cuenta LLave MX para autenticación, Información y participación ciudadana
Content quality
good
Branding
consistent

Technology

Stack
JavaServer Faces (jakarta.faces.resource), PrimeFaces 14.0.12, jQuery, Swiper.js, Google Fonts, Google Tag Manager
Frameworks
PrimeFaces, Jakarta Faces
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by https URLs)
  • Secure cookies settings (SameSite=Strict)
  • Use of Google Tag Manager asynchronously
  • No visible exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Official Mexican government portal for federal procedures and social programs.
  2. Content is in Spanish and targeted at Mexican citizens.
  3. No signs of phishing, malware, or suspicious activity.
  4. Good use of modern web technologies and frameworks.
  5. Lacks explicit cookie consent mechanism despite GDPR relevance.
  6. No visible contact emails or phone numbers on the homepage.
  7. Social media presence is linked to official government accounts.
  8. No security.txt or vulnerability disclosure page found.
Technical notes

Notes

The website is built on a JavaServer Faces framework with PrimeFaces UI components, indicating a robust enterprise-grade technology stack. It uses modern JavaScript libraries like jQuery and Swiper.js for interactivity and responsive design. Google Fonts and Google Tag Manager are integrated for typography and analytics. Hosting is likely via Akamai CDN, providing performance and security benefits. The site is mobile optimized and SEO friendly with proper meta tags and Open Graph data. There is room for improvement in accessibility and cookie management. Overall, the technical infrastructure is solid and well maintained.
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 gob.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 gob.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.