Domain Risk HeatMap

Define a Permissions-Policy header that disables unused browser features and only allows required capabilities.

Example restrictive baseline:

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(self)

Adapt the policy to the site:

• Disable features not used by the website.
• Allow features only for self or specific trusted origins when required.
• Review embedded third-party content, including videos, maps, service widgets and marketing tools.
• Test user journeys that may require browser permissions.
• Document intentional exceptions.

Common directives to review:

• camera
• microphone
• geolocation
• payment
• usb
• fullscreen
• autoplay
• clipboard-read
• clipboard-write

Reduce unnecessary software version disclosure in HTTP response headers.

Recommended actions:

1. Identify the component exposing the version through the x-powered-by header.

   Example:

   curl -I https://example.com
   

2. Disable or minimize version disclosure.

   Nginx:

   server_tokens off;
   

   Apache:

   ServerTokens Prod
   ServerSignature Off
   

   PHP:

   expose_php = Off
   

3. If the header is generated by a framework, CMS, proxy, CDN, or plugin, remove or override the version at that layer.

4. Keep generic product disclosure only where operationally required.

   Prefer:

   Server: nginx
   

   Instead of:

   Server: nginx/1.18.0
   

5. Validate the result after deployment:

   curl -I https://example.com
   

6. Do not rely on header hiding as a security control. Also verify that the disclosed component is updated, supported, and not affected by known vulnerabilities.

Adopt modern image formats across the site, starting with the images that have the greatest performance impact.

Technical recommendations:

• Audit the current image weight and sort images by transferred size.
• Prioritize:
  • Main homepage or hero image.
  • Promotional banners.
  • Category images.
  • Main content images.
  • Carousels and visual modules loaded during the initial render.
• Convert suitable JPEG/PNG assets to WebP or AVIF using controlled compression.
• Keep JPEG/PNG fallbacks if additional compatibility is required:

  <picture>
    <source srcset="/image.avif" type="image/avif">
    <source srcset="/image.webp" type="image/webp">
    <img src="/image.jpg" alt="Image description">
  </picture>
  

• Configure automatic generation through the CMS, server, CDN, or deployment pipeline.
• Avoid uploading oversized images to the CMS.
• Use srcset and sizes to serve versions adapted to each viewport:

  <img
    src="/content-800.webp"
    srcset="/content-400.webp 400w, /content-800.webp 800w, /content-1200.webp 1200w"
    sizes="(max-width: 768px) 100vw, 50vw"
    alt="Content image description">
  

• Use loading="lazy" for non-critical images.
• Do not lazy-load the main image if it contributes to LCP.
• Measure before and after with Lighthouse, PageSpeed Insights, or WebPageTest to validate the real reduction in page weight and loading time.

Manually verify whether a privacy policy exists and is easy to access from the analysed page.

Recommended technical actions:

1. Add a persistent footer link using clear wording such as:

   • Privacy Policy
   • Privacy Notice
   • Data Protection
   • Localised equivalents where appropriate, for example Política de privacidad.

2. Ensure the link is present in the initial HTML where possible, not only injected after user interaction.

3. Use a stable, crawlable URL, for example:

   • /privacy-policy
   • /privacy
   • /politica-de-privacidad

4. Confirm that the linked page returns HTTP 200, is indexable if appropriate, and is not blocked by authentication, geolocation or JavaScript-only navigation.

5. Manually review the legal content with the responsible legal/privacy team. This automated indicator only checks discoverability, not legal sufficiency.

Provide an accessible name for every interactive link and button.

Recommended implementation:

<a href="/account" aria-label="View account">
  <svg aria-hidden="true">...</svg>
</a>

<button aria-label="Close dialog">×</button>

Technical checks:

• Prefer visible text content over aria-label when possible.
• For icon-only controls, add aria-label or visually hidden text.
• Ensure decorative icons inside the control use aria-hidden="true".
• Avoid generic labels such as "click here" or "read more" without context.
• Re-test with a screen reader or accessibility browser extension.

Publish a security.txt file with a clear vulnerability reporting process.

Recommended actions:

1. Create the file at the standard location:

   https://example.com/.well-known/security.txt
   

2. Include at least a valid contact method.

   Example:

   Contact: mailto:security@example.com
   Preferred-Languages: en, es
   Canonical: https://example.com/.well-known/security.txt
   

3. Optional but recommended fields:

   Policy: https://example.com/security-policy
   Acknowledgments: https://example.com/security-acknowledgments
   Expires: 2027-12-31T23:59:59Z
   

4. Make sure the contact mailbox is monitored.

5. Define an internal triage process:

   • Who receives the report
   • Who validates the issue
   • Expected response time
   • Escalation path for critical vulnerabilities
   • Criteria for coordinated disclosure

6. Verify publication:

   curl -I https://example.com/.well-known/security.txt
   curl https://example.com/.well-known/security.txt
   

Enable DNSSEC signing for the domain.

Recommended technical actions:

1. Confirm DNSSEC support with the current DNS hosting provider or registrar.
2. Enable DNSSEC signing on the authoritative DNS zone.
3. Publish the resulting DS record with the domain registrar so the parent zone can delegate trust.
4. Verify propagation and validate the chain of trust with an external DNSSEC validation tool.
5. Monitor key rotation schedules if the provider does not automate them.