peopleperhour.com

Readiness by lane

Green: peopleperhour.com. Thin bar: Job Portals, HR & Recruitment peer median.

Priority fixes for peopleperhour.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 30 days, below the one-year benchmark.

   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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   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 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

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

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Amazon had a 394-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

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

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for peopleperhour.com, 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.

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

   Guide: HTTPS and TLS Guide for Website Owners

What peopleperhour.com already does well

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

• security.txt publishedsecurity.txt with a contact found.6.2% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers
• Referrer-Policy setReferrer-Policy present.31% of peers

What we saw

Homepage checked

https://www.peopleperhour.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 394-day validity, expiring 2027-02-22

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 30 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

640 KB, gzip

Images on homepage

65 (jpg 72, webp 34, png 25)

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

• concursosnobrasil.com82
• hackerrank.com82
• jobberman.com82
• praca.pl82
• resume.io81

Job Portals, HR & Recruitment readiness benchmark