城市(city): unknown
省份(region): unknown
国家(country): None
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 140.149.213.19
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45771
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;140.149.213.19. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021901 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 03:08:18 CST 2025
;; MSG SIZE rcvd: 107Host 19.213.149.140.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 19.213.149.140.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 35.196.39.187 | attackbotsspam | [Thu Apr 09 19:58:24.141239 2020] [:error] [pid 21672:tid 140306501166848] [client 35.196.39.187:42106] [client 35.196.39.187] ModSecurity: Access denied with code 403 (phase 1). Match of "within %{tx.allowed_http_versions}" against "REQUEST_PROTOCOL" required. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "972"] [id "920430"] [msg "HTTP protocol version is not allowed by policy"] [data "HTTP/1.0"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/POLICY/PROTOCOL_NOT_ALLOWED"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.10"] [hostname "staklim-malang.info"] [uri "/robots.txt"] [unique_id "Xo8b8EfyFjPtNck1w0KN5AAAAfA"]
... |
2020-04-10 03:43:39 |
| 138.197.129.38 | attackspam | Apr 9 19:51:38 odroid64 sshd\[15485\]: Invalid user steam from 138.197.129.38 Apr 9 19:51:38 odroid64 sshd\[15485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.129.38 ... |
2020-04-10 03:36:38 |
| 94.191.57.62 | attackbotsspam | $lgm |
2020-04-10 03:31:36 |
| 182.151.23.170 | attack | Unauthorized connection attempt detected from IP address 182.151.23.170 to port 6379 |
2020-04-10 03:30:00 |
| 188.128.39.127 | attackbots | 2020-04-09T21:17:51.763294ns386461 sshd\[21185\]: Invalid user a from 188.128.39.127 port 54506 2020-04-09T21:17:51.767810ns386461 sshd\[21185\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.39.127 2020-04-09T21:17:53.873361ns386461 sshd\[21185\]: Failed password for invalid user a from 188.128.39.127 port 54506 ssh2 2020-04-09T21:32:09.001346ns386461 sshd\[2163\]: Invalid user sftp from 188.128.39.127 port 59490 2020-04-09T21:32:09.005773ns386461 sshd\[2163\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.39.127 ... |
2020-04-10 03:35:56 |
| 217.182.67.242 | attackspambots | Apr 9 21:19:13 silence02 sshd[18579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.67.242 Apr 9 21:19:15 silence02 sshd[18579]: Failed password for invalid user rails from 217.182.67.242 port 57959 ssh2 Apr 9 21:23:37 silence02 sshd[19028]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.67.242 |
2020-04-10 03:29:33 |
| 222.186.175.163 | attackspambots | 2020-04-09T19:39:03.666380shield sshd\[10139\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.163 user=root 2020-04-09T19:39:05.063884shield sshd\[10139\]: Failed password for root from 222.186.175.163 port 13100 ssh2 2020-04-09T19:39:08.097172shield sshd\[10139\]: Failed password for root from 222.186.175.163 port 13100 ssh2 2020-04-09T19:39:10.874509shield sshd\[10139\]: Failed password for root from 222.186.175.163 port 13100 ssh2 2020-04-09T19:39:14.401840shield sshd\[10139\]: Failed password for root from 222.186.175.163 port 13100 ssh2 |
2020-04-10 03:41:25 |
| 219.143.182.178 | attackbots | (eximsyntax) Exim syntax errors from 219.143.182.178 (CN/China/178.182.143.219.broad.bj.bj.dynamic.163data.com.cn): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-04-09 17:29:03 SMTP call from [219.143.182.178] dropped: too many syntax or protocol errors (last command was "?\034?\032?\027?\031?\034?\033?\030?\032?\026?\016?\r?\v?\f? ?") |
2020-04-10 03:12:54 |
| 51.158.96.229 | attack | Apr 9 15:47:02 vps647732 sshd[20486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.158.96.229 Apr 9 15:47:05 vps647732 sshd[20486]: Failed password for invalid user user from 51.158.96.229 port 46348 ssh2 ... |
2020-04-10 03:06:02 |
| 104.248.159.69 | attack | Jan 25 23:30:08 woltan sshd[21096]: Failed password for invalid user mysql from 104.248.159.69 port 40518 ssh2 |
2020-04-10 03:11:56 |
| 222.186.31.166 | attackspambots | Apr 9 19:23:25 scw-6657dc sshd[5030]: Failed password for root from 222.186.31.166 port 37123 ssh2 Apr 9 19:23:25 scw-6657dc sshd[5030]: Failed password for root from 222.186.31.166 port 37123 ssh2 Apr 9 19:23:27 scw-6657dc sshd[5030]: Failed password for root from 222.186.31.166 port 37123 ssh2 ... |
2020-04-10 03:25:25 |
| 138.99.7.54 | attackspambots | Apr 9 15:38:06 santamaria sshd\[12892\]: Invalid user data from 138.99.7.54 Apr 9 15:38:06 santamaria sshd\[12892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.99.7.54 Apr 9 15:38:08 santamaria sshd\[12892\]: Failed password for invalid user data from 138.99.7.54 port 55902 ssh2 ... |
2020-04-10 03:15:04 |
| 76.214.112.45 | attackbotsspam | Apr 9 17:39:38 jupiter sshd[11796]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=76.214.112.45 Apr 9 17:39:40 jupiter sshd[11796]: Failed password for invalid user time from 76.214.112.45 port 24532 ssh2 ... |
2020-04-10 03:16:25 |
| 222.186.30.112 | attackbotsspam | 20/4/9@14:57:26: FAIL: Alarm-SSH address from=222.186.30.112 ... |
2020-04-10 03:16:03 |
| 43.226.147.219 | attack | SSH Brute-Force reported by Fail2Ban |
2020-04-10 03:39:08 |