Jobluvo's application agent
Jobluvo sends job applications for the people who use it. When it does, a program runs a browser that fills the employer's application form and presses submit. This page says what that agent is and how a site can recognise it.
What it does
It opens the application form of one job a person chose, fills it from facts that person confirmed, and presses submit once. It sends an application only after the person approved that application in Jobluvo. It sends one application at a time, and no more in a day than the person's account allows.
What it never does
It never solves a CAPTCHA or uses a service that does. It never disguises its browser or changes its address to get past a check. It never sends an application nobody approved, and it reads nothing but the application form it was sent to.
How to recognise it
Every request its browser sends while it applies is signed with an HTTP message signature, as Web Bot Auth describes (RFC 9421): the form's page and every file, frame and call the page makes. So is the one request it makes outside the browser, for a job's questions. Its browser runs no service workers, so nothing a page starts goes around the signature. A WebSocket connection is the one thing it cannot sign. Every request leaves from one of two fixed addresses.
| What | Value |
|---|---|
| Signature-Agent header | "https://jobluvo.com" |
| Signature-Input and Signature headers | Over the request's host and the Signature-Agent header, Ed25519, tagged web-bot-auth |
| Public key | https://jobluvo.com/.well-known/http-message-signatures-directory |
| Addresses | 209.71.81.228 and 2a09:8280:e618:1:0:19b:73cf:0 |
| Browser | Chromium, driven by Playwright, with Chromium's own user agent followed by the token below, and no service workers |
| User agent token | JobluvoAgent/1.0 (+https://jobluvo.com/agent) |
If it causes you a problem
Write to info@jobluvo.com with the site and the time. Jobluvo will look at it.