felizes.pt

Readiness by lane

Green: felizes.pt. Thin bar: Dating Apps peer median.

Priority fixes for felizes.pt

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for felizes.pt was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   42% of Dating Apps peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   22% of Dating Apps peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   23% of Dating Apps peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   18% of Dating Apps peers do this.

   Guide: CDN Guide for Website Owners

What felizes.pt already does well

Practices fewer than half of Dating Apps peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.8.3% of peers
• Modern image formats in useWebP or AVIF images detected.27% of peers
• Structured data presentJSON-LD structured data found.29% of peers

What we saw

Homepage checked

https://felizes.pt/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

ZeroSSL, 90-day validity, expiring 2026-12-24

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

169 KB, gzip

Images on homepage

38 (jpg 35, webp 4, svg 3, png 3)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Dating Apps sites

• badoo.com76
• dateinasia.com76
• dating.com75
• flirtify.com76
• novamora.nl77

Dating Apps readiness benchmark