wbjeeb.nic.in

Readiness by lane

Green: wbjeeb.nic.in. Thin bar: Government Services peer median.

Priority fixes for wbjeeb.nic.in

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://wbjeeb.nic.in/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   On WordPress: Set both WordPress Address and Site Address to https:// in Settings > General, then add the server or CDN redirect.

   88% of Government Services peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   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.

   77% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.wbjeeb.nic.in.

   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.

   Guide: A Practical Website Health Check for Owners

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

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

What wbjeeb.nic.in already does well

Practices fewer than half of Government Services peers use.

• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.34% of peers
• Referrer-Policy setReferrer-Policy present.39% of peers
• Content Security Policy presentContent-Security-Policy present.41% of peers

What we saw

Homepage checked

https://wbjeeb.nic.in/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

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

Platform or framework

WordPress

HSTS

max-age 365 days, includeSubDomains

Homepage HTML

85 KB, gzip

Images on homepage

11 (png 6, svg 4, jpg 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

Compare with other Government Services sites

• baohiemxahoi.gov.vn49
• bsaonline.com49
• simple.sv50
• slbfe.lk50
• upmsp.edu.in50

Government Services readiness benchmark