xn--80aapampemcchfmo7a3c9ehj.xn--p1ai

Readiness by lane

Green: xn--80aapampemcchfmo7a3c9ehj.xn--p1ai. Thin bar: Government Services peer median.

Priority fixes for xn--80aapampemcchfmo7a3c9ehj.xn--p1ai

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.xn--80aapampemcchfmo7a3c9ehj.xn--p1ai.

   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 Government 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 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for xn--80aapampemcchfmo7a3c9ehj.xn--p1ai, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   17% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   11% of Government Services peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   8% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

What xn--80aapampemcchfmo7a3c9ehj.xn--p1ai already does well

Practices fewer than half of Government Services peers use.

• Modern image formats in useWebP or AVIF images detected.15% of peers
• Structured data presentJSON-LD structured data found.15% of peers
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.34% of peers

What we saw

Homepage checked

https://xn--80aapampemcchfmo7a3c9ehj.xn--p1ai/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-11

Platform or framework

Bitrix

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

Homepage HTML

777 KB, gzip

Images on homepage

44 (jpg 17, webp 14, svg 10)

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 Government Services sites

• cpf.gov.sg82
• justice.gov81
• mybharat.gov.in81
• wien.gv.at82
• www.gov.uk82

Government Services readiness benchmark