fivepost.ru

Readiness by lane

Green: fivepost.ru. Thin bar: Postage & Courier Services peer median.

Priority fixes for fivepost.ru

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.fivepost.ru.

   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.

   52% of Postage & Courier Services 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 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   44% of Postage & Courier Services peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 3 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Next.js: The next/image component serves optimized formats automatically.

   31% of Postage & Courier Services peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

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

   On Next.js: Next.js documents nonce-based CSP with middleware.

   31% of Postage & Courier Services peers do this.

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

What fivepost.ru already does well

Practices fewer than half of Postage & Courier Services peers use.

• Nameservers spread across providersNameservers spread across more than one operator.12% of peers
• Referrer-Policy setReferrer-Policy present.28% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.39% of peers

What we saw

Homepage checked

https://fivepost.ru/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Hellenic Academic and Research Institutions CA, 198-day validity, expiring 2027-02-06

Platform or framework

Next.js

DNS operators

RU-CENTER DNS, plus 1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

Homepage HTML

39 KB, gzip

Images on homepage

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 Postage & Courier Services sites

• dhl.de66
• indiapost.gov.in66
• shalom.com.pe66
• spx.ph67
• zoom.red67

Postage & Courier Services readiness benchmark