STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

freemail.hu

freemail.hu's public homepage, certificate and DNS checked against 31 practices and compared with 33 Webmail & Message Inboxes sites.

Readiness index
41/100

Webmail & Message Inboxes median 64

Ahead of
15%

of measured Webmail & Message Inboxes sites

Practices observed
8/29

2 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:11:36 UTC from one location. How we measure

Readiness by lane

Green: freemail.hu. Thin bar: Webmail & Message Inboxes peer median.

Enable

26/100

Peers 60

Harden

38/100

Peers 67

Accelerate

70/100

Peers 54

Recover

0/100

Peers 19

Priority fixes for freemail.hu

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

  1. Priority 1 · Harden

    HSTS kept for at least a year

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

    Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

    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.

    On Next.js: Add the header in the headers() option of next.config.js for all routes.

    61% of Webmail & Message Inboxes peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.freemail.hu.

    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.

    58% of Webmail & Message Inboxes peers do this.

  3. Priority 3 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    58% of Webmail & Message Inboxes peers do this.

  4. Priority 4 · Enable

    Meta description written

    Observed: The homepage had no meta description.

    What to do: Write a short, specific description of the page for people, not a list of keywords.

    82% of Webmail & Message Inboxes peers do this.

What freemail.hu already does well

Practices fewer than half of Webmail & Message Inboxes peers use.

  • Static files cached for 30 days or moreLong-lived caching on static files.28% of peers

What we saw

Homepage checked
https://freemail.hu/
Homepage response
HTTP 200, after 2 redirects
TLS
TLSv1.3, HTTP/2
Certificate
Microsec Ltd., 396-day validity, expiring 2026-11-22
Platform or framework
Next.js
DNS operators
1 self-run or other nameserver domain
Homepage HTML
32 KB, gzip
Images on homepage
1 (svg 1)

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 freemail.hu?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: freemail.hu. This profile covers configuration only.

Compare with other Webmail & Message Inboxes sites