城市(city): unknown
省份(region): unknown
国家(country): Canada
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 68.150.30.216
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34885
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;68.150.30.216. IN A
;; AUTHORITY SECTION:
. 243 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023052800 1800 900 604800 86400
;; Query time: 74 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 28 16:30:50 CST 2023
;; MSG SIZE rcvd: 106
Host 216.30.150.68.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 216.30.150.68.in-addr.arpa: NXDOMAIN
IP | 类型 | 评论内容 | 时间 |
---|---|---|---|
222.186.31.83 | attackspam | Feb 17 03:22:15 * sshd[29526]: Failed password for root from 222.186.31.83 port 13256 ssh2 |
2020-02-17 10:32:37 |
196.219.237.106 | attackbotsspam | MultiHost/MultiPort Probe, Scan, Hack - |
2020-02-17 13:13:20 |
67.229.93.31 | attackspambots | 67.229.93.31 was recorded 5 times by 4 hosts attempting to connect to the following ports: 11211. Incident counter (4h, 24h, all-time): 5, 18, 126 |
2020-02-17 10:30:56 |
138.68.234.162 | attack | Feb 17 01:17:19 server sshd\[1678\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.234.162 user=root Feb 17 01:17:21 server sshd\[1678\]: Failed password for root from 138.68.234.162 port 35718 ssh2 Feb 17 01:23:30 server sshd\[2820\]: Invalid user wch from 138.68.234.162 Feb 17 01:23:30 server sshd\[2820\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.234.162 Feb 17 01:23:32 server sshd\[2820\]: Failed password for invalid user wch from 138.68.234.162 port 46056 ssh2 ... |
2020-02-17 10:34:51 |
167.114.118.135 | attackspambots | WordPress login Brute force / Web App Attack on client site. |
2020-02-17 10:30:35 |
171.240.145.119 | attack | Automatic report - Port Scan Attack |
2020-02-17 13:11:26 |
46.88.133.99 | attackspambots | Feb 17 05:59:44 vpn01 sshd[31975]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.88.133.99 Feb 17 05:59:46 vpn01 sshd[31975]: Failed password for invalid user jtpotato from 46.88.133.99 port 50366 ssh2 ... |
2020-02-17 13:12:41 |
183.91.68.148 | attack | Brute force attack stopped by firewall |
2020-02-17 10:32:50 |
173.241.7.235 | attackbots | SSH login attempts. |
2020-02-17 13:01:00 |
112.85.42.227 | attackbotsspam | Feb 16 21:14:36 NPSTNNYC01T sshd[9179]: Failed password for root from 112.85.42.227 port 46349 ssh2 Feb 16 21:18:10 NPSTNNYC01T sshd[9256]: Failed password for root from 112.85.42.227 port 49457 ssh2 ... |
2020-02-17 10:28:03 |
61.69.78.78 | attackspambots | Automatic report - Banned IP Access |
2020-02-17 10:38:26 |
189.208.60.230 | attackbotsspam | MultiHost/MultiPort Probe, Scan, Hack - |
2020-02-17 10:32:06 |
165.22.240.146 | attackspambots | Feb 17 01:23:22 legacy sshd[18156]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.240.146 Feb 17 01:23:24 legacy sshd[18156]: Failed password for invalid user teamspeak3 from 165.22.240.146 port 58058 ssh2 Feb 17 01:26:46 legacy sshd[18344]: Failed password for sshd from 165.22.240.146 port 58304 ssh2 ... |
2020-02-17 10:47:17 |
69.51.0.66 | attack | Feb 17 05:32:16 ns382633 sshd\[30022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.51.0.66 user=root Feb 17 05:32:18 ns382633 sshd\[30022\]: Failed password for root from 69.51.0.66 port 32893 ssh2 Feb 17 05:59:45 ns382633 sshd\[1850\]: Invalid user semenov from 69.51.0.66 port 46371 Feb 17 05:59:45 ns382633 sshd\[1850\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.51.0.66 Feb 17 05:59:47 ns382633 sshd\[1850\]: Failed password for invalid user semenov from 69.51.0.66 port 46371 ssh2 |
2020-02-17 13:06:12 |
182.1.115.182 | attackspam | [Mon Feb 17 05:23:14.630935 2020] [:error] [pid 22230:tid 139656805431040] [client 182.1.115.182:62470] [client 182.1.115.182] ModSecurity: Access denied with code 403 (phase 4). Pattern match "^5\\\\d{2}$" at RESPONSE_STATUS. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/RESPONSE-950-DATA-LEAKAGES.conf"] [line "118"] [id "950100"] [msg "The Application Returned a 500-Level Status Code"] [data "Matched Data: 500 found within RESPONSE_STATUS: 500"] [severity "ERROR"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-disclosure"] [tag "WASCTC/WASC-13"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.6"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/citra-satelit-bmkg"] [unique_id "XknAyUDcx7KffueAQ4GEkgAAAAE"], referer: https://www.google.com/ ... |
2020-02-17 10:48:28 |