Check an IP Address, Domain Name, Subnet, or ASN
35.216.140.3 has a threat confidence score of 100%. This IP address from Switzerland (AS15169, Google LLC) has been observed in 1,424 honeypot sessions and reported 6 times targeting FTP, HTTPS, HTTP, MONGODB, SSH and 4 other protocols. Detected attack patterns include http dotenv file exposure probe, https dotenv environment file exposure probe, http git repository config exposure probe. First observed on January 20, 2026, most recently active April 12, 2026.
Identifies HTTP GET requests targeting the /.env file, indicating attempts to access exposed environment configuration files commonly containing application secrets such as database credentials, API keys, and service tokens.
Identifies an HTTPS request targeting a .env file in the web root or application directory. Access attempts to /.env indicate automated scanning for exposed environment configuration files that may contain application secrets, database credentials, API keys, or cloud tokens. This probe is commonly associated with opportunistic internet-wide scanning for misconfigured web deployments.
Identifies HTTP GET requests targeting /.git/config, indicating attempts to access exposed Git repository configuration files. Successful access may enable repository reconstruction, credential harvesting, or source code disclosure.
Identifies RDP clients attempting authentication using Network Level Authentication (NLA) with the NTLM challenge-response protocol. This occurs during the CredSSP negotiation phase before a remote desktop session is established and indicates an active credential authentication attempt against the RDP service
Identifies an HTTPS request targeting the .git/config file within a web-accessible repository directory. Access attempts to /.git/config indicate automated repository exposure scanning intended to retrieve remote origin URLs, repository structure, and potentially credential-bearing configuration data. This is a common reconnaissance technique used to identify misconfigured web servers exposing version control metadata.
FTP session where an empty control-channel command is observed in conjunction with non-printable binary data on the control channel. This pattern reflects malformed or non-FTP-compliant input, commonly seen during TLS handshake attempts on plaintext endpoints, protocol confusion, or automated scanner misfires.
HTTP request using GET method.
Identifies HTTP requests targeting the web server root path ("/"), typically used for initial service discovery, host validation, or baseline content inspection prior to deeper enumeration.
Identifies HTTP GET requests directly targeting the /bad-request path, indicating automated or manual probing of application error-handling routes rather than legitimate navigation flow.
Identifies HTTPS requests targeting the web server root path ("/"), typically used for initial service discovery, host validation, or baseline content inspection prior to deeper enumeration
| Reporter | Date | Category | Protocol | Comment |
|---|---|---|---|---|
| User | Mar 20, 2026, 14:51 | Brute Force | SMB | SikkerGuard: 2 blocked packets |
| User | Mar 12, 2026, 07:47 | Brute Force | DOCKER | SikkerGuard: 2 blocked packets |
| User | Mar 10, 2026, 14:34 | Brute Force | SSH | SikkerGuard: 2 blocked packets |
| User | Mar 6, 2026, 02:41 | Brute Force | FTP | SikkerGuard: 2 blocked packets |
| User | Mar 5, 2026, 10:11 | Brute Force | SMB | SikkerGuard: 2 blocked packets |