35.195.85.59

Blocked Relentless Regular Toolkit

Blocked since UTC, no end date. Our servers refuse it, web requests included, and it is in feed.txt.

Record

Score
49/100each request counts half as much after 30 days
Worst level
Relentless
Attack-shaped requests
380all time
Active days
4UTC days
First seen
Last seen
Servers hit
8
Targets
10sites
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 380 attack-shaped requests across 4 separate days.

Its traffic requested a .env file, hoping to find API keys or database credentials (249 requests); it also requested the .git directory itself, hoping it is exposed and browsable (34); it also probed for an exposed .git directory to download the site's source history and config (15).

Seen by our edge and web sensors, against 10 of the sites we watch, among them 4emx.com, bursukov.com, haiv.dev, homocontinum.com and odor-ex.com.

Scored into the "Relentless" level, its highest so far. Badges: Regular and Toolkit.

Its busiest hour on record began UTC, with 92 requests.

Routed via AS396982 (Google LLC), a cloud network.

Surfaces: web-app. Attack types: scanning, hunting for secrets, unclassified. Seen by: edge, web.

Activity, last 90 days

Active on 4 of the last 90 UTC days. Current block: , with no end date.

Daily counts
Attack requests per UTC day, days with activity only
Day (UTC)Requests
135
96
123
26
  • At least 92 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 944, POST 10, HEAD 9.
  • The servers we watch answered: 403 46, 404 46 (totals only, from our web servers).

Evidence

Newest first, the latest 50 stored requests grouped into runs. Times are UTC. The user agent is shown as its family only.

Evidence, newest first, grouped by UTC day
TimeSiteWhat happenedRequestUser agentSeen by
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /config/parameters.ymlbrowser claimedge
servbg.comrequested the .git directory itself, hoping it is exposed and browsableGET /.git/COMMIT_EDITMSGbrowser claimedge
servbg.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswdbrowser claimedge
servbg.com5× was turned away at the edge because the address is already on our block list; not counted as new evidence (5 distinct paths)GET /vercel.jsonbrowser claimedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /admin/.envbrowser claimedge
servbg.com3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)GET /.docker/config.jsonbrowser claimedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.developmentbrowser claimedge
servbg.com3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)GET /app/etc/env.phpbrowser claimedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidencePOST /browser claimedge
servbg.comprobed a Spring Boot actuator endpoint, which can leak environment variables and internal config if left openGET /actuator/configpropsbrowser claimedge
servbg.comrequested the .git directory itself, hoping it is exposed and browsableGET /.git/refs/heads/stagingbrowser claimedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.s3cfgbrowser claimedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceHEAD /browser claimedge
servbg.com4× was turned away at the edge because the address is already on our block list; not counted as new evidence (4 distinct paths)GET /sites/default/settings.phpbrowser claimedge
servbg.comrequested the .git directory itself, hoping it is exposed and browsableGET /.git/FETCH_HEADbrowser claimedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.distbrowser claimedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.github/workflows/ci.ymlbrowser claimedge
servbg.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /core/.envbrowser claimedge
servbg.com5× was turned away at the edge because the address is already on our block list; not counted as new evidence (5 distinct paths)GET /auth.jsonbrowser claimedge
servbg.comrequested the .git directory itself, hoping it is exposed and browsableGET /.git/info/refsbrowser claimedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /env.txtbrowser claimedge
servbg.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/home/ubuntu/.aws/credentialsbrowser claimedge
servbg.comrequested the .git directory itself, hoping it is exposed and browsableGET /.git/logs/refs/heads/masterbrowser claimedge
servbg.com3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)GET /app/etc/local.xmlbrowser claimedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /web/.envbrowser claimedge
servbg.com7× was turned away at the edge because the address is already on our block list; not counted as new evidence (7 distinct paths)GET /.codeium/windsurf/mcp_config.jsonbrowser claimedge

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
59.85.195.35.bc.googleusercontent.com
Country
Belgium BE
Flags
cloud range (GCP)
Abuse contact
found in the registry
Checked

Elsewhere: GreyNoise, Shodan, AbuseIPDB.

Your verdict

What readers make of this address. Verdicts are opinions of signed-in Academy members. They never change blocking or reporting.

No verdicts yet.

Every listing carries its evidence on its page, and blocks are lifted only by us; if you were blocked and have fixed the cause, write to abuse-reports@abuse.servbg.com.