STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

jecontacte.com

jecontacte.com's public homepage, certificate and DNS checked against 31 practices and compared with 218 Dating Apps sites.

Readiness index
43/100

Dating Apps median 58

Ahead of
17%

of measured Dating Apps sites

Practices observed
9/29

2 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 12:18:04 UTC from one location. How we measure

Readiness by lane

Green: jecontacte.com. Thin bar: Dating Apps peer median.

Enable

49/100

Peers 71

Harden

31/100

Peers 52

Accelerate

59/100

Peers 53

Recover

0/100

Peers 7

Priority fixes for jecontacte.com

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

  1. Priority 1 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    82% of Dating Apps peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    64% of Dating Apps peers do this.

  3. Priority 3 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.jecontacte.com.

    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.

  4. Priority 4 · 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.

What we saw

Homepage checked
https://www.jecontacte.com/
Homepage response
HTTP 200
TLS
TLSv1.2, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2027-02-05
DNS operators
Amazon Route 53
Homepage HTML
55 KB, gzip
Images on homepage
12 (jpg 12)

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

Own jecontacte.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: jecontacte.com. This profile covers configuration only.

Compare with other Dating Apps sites