2a05:4140:3::4ecc

Blocked Scanner Toolkit

Blocked since UTC, no end date. Its /64 prefix is in feed.txt.

Record

Score
32/100each request counts half as much after 30 days
Worst level
Scanner
Attack-shaped requests
13all time
Active days
1UTC days
First seen
Last seen
Servers hit
1
Targets
1site
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 13 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (8 requests); it also probed for an exposed GraphQL endpoint or its config file, often a precursor to an introspection query (2); it also swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner (1).

Seen by our web sensor, against haived.com.

Scored into the "Scanner" level, its highest so far. Badge: Toolkit.

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

Routed via AS212271 (Lumanex Srl), a home broadband network.

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

Activity, last 90 days

Active on 1 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
13
  • At least 13 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 16.
  • The servers we watch answered: 404 11, 301 5 (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
haived.com2× made a request that matched no known pattern (2 distinct paths)GET /api/adminbrowser claimweb
haived.comrequested a common cloud/app secrets or credentials filename (AWS, GCP, Firebase, Kubernetes service-account token, SSH, master key) from a wordlist, hoping one was left in the webrootGET /next.config.jsbrowser claimweb
haived.commade a request that matched no known patternGET /api/auth/configbrowser claimweb
haived.comrequested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticatedGET /api/configbrowser claimweb
haived.comprobed for an exposed GraphQL endpoint or its config file, often a precursor to an introspection queryGET /graphqlbrowser claimweb
haived.comprobed for an exposed GraphQL endpoint or its config file, often a precursor to an introspection queryGET /graphqlbrowser claimweb
haived.comswept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scannerGET /api/browser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.developmentbrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.developmentbrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.productionbrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.productionbrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.localbrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.localbrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.envbrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.envbrowser claimweb

Network

ASN
AS212271 Lumanex Srl
Network type
home broadband
Reverse DNS
it-pom.server-by.c1vhosting.it
Country
Italy IT
Flags
none observed
Abuse contact
not found
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.