crowdworks.jp

Readiness by lane

Green: crowdworks.jp. Thin bar: Job Portals, HR & Recruitment peer median.

Priority fixes for crowdworks.jp

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.

   36% of Job Portals, HR & Recruitment peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

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

   34% of Job Portals, HR & Recruitment peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   58% of Job Portals, HR & Recruitment peers do this.

   Guide: Structured Data Basics for Website Owners

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.

   30% of Job Portals, HR & Recruitment peers do this.

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

What crowdworks.jp already does well

Practices fewer than half of Job Portals, HR & Recruitment peers use.

• Referrer-Policy setReferrer-Policy present.31% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.45% of peers
• Framing restrictedFraming controls present.47% of peers

What we saw

Homepage checked

https://crowdworks.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-01

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

24 KB, gzip

Images on homepage

0

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 Job Portals, HR & Recruitment sites

• bestjobs.eu74
• charityjob.co.uk74
• jobindex.dk74
• keejob.com74
• welcometothejungle.com75

Job Portals, HR & Recruitment readiness benchmark