City: unknown
Region: unknown
Country: South Africa
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 197.229.125.136
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15296
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;197.229.125.136. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020600 1800 900 604800 86400
;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 23:43:18 CST 2025
;; MSG SIZE rcvd: 108
136.125.229.197.in-addr.arpa domain name pointer 8ta-229-125-136.telkomadsl.co.za.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
136.125.229.197.in-addr.arpa name = 8ta-229-125-136.telkomadsl.co.za.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
213.133.3.8 | attackbotsspam | Sep 24 07:07:45 tuotantolaitos sshd[32143]: Failed password for root from 213.133.3.8 port 35935 ssh2 ... |
2019-09-24 17:01:01 |
122.242.198.138 | attack | Web application attack detected by fail2ban |
2019-09-24 17:19:18 |
41.34.8.248 | attackspam | Unauthorised access (Sep 24) SRC=41.34.8.248 LEN=40 TTL=53 ID=8907 TCP DPT=8080 WINDOW=23001 SYN |
2019-09-24 17:15:28 |
211.54.40.81 | attackbotsspam | Automatic report - Banned IP Access |
2019-09-24 16:47:42 |
49.143.95.121 | attackbotsspam | [TueSep2405:52:27.1114172019][:error][pid26675:tid47560302733056][client49.143.95.121:44905][client49.143.95.121]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"\\\\\\\\.sql\$"atREQUEST_FILENAME.[file"/etc/apache2/conf.d/modsec_rules/10_asl_rules.conf"][line"1288"][id"350590"][rev"2"][msg"Atomicorp.comWAFRules:AttackBlocked-Dataleakage-attempttoaccessrawSQLfiles\(disablethisruleifyourequireaccesstofilesthatendwith.sql\)"][severity"CRITICAL"][hostname"boltonholding.com"][uri"/boltonholding.sql"][unique_id"XYmS@yUY647fdT5XzKC6LAAAABU"][TueSep2405:52:29.4647092019][:error][pid26753:tid47560302733056][client49.143.95.121:45164][client49.143.95.121]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"\\\\\\\\.sql\$"atREQUEST_FILENAME.[file"/etc/apache2/conf.d/modsec_rules/10_asl_rules.conf"][line"1288"][id"350590"][rev"2"][msg"Atomicorp.comWAFRules:AttackBlocked-Dataleakage-attempttoaccessrawSQLfiles\(disablethisruleifyourequireaccesstofilesthatendwith.sql\)"][sever |
2019-09-24 16:41:30 |
218.92.0.188 | attackspambots | $f2bV_matches |
2019-09-24 16:39:46 |
202.107.238.94 | attack | Sep 24 10:15:40 v22019058497090703 sshd[24473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.107.238.94 Sep 24 10:15:41 v22019058497090703 sshd[24473]: Failed password for invalid user testuser from 202.107.238.94 port 39546 ssh2 Sep 24 10:20:53 v22019058497090703 sshd[24892]: Failed password for test from 202.107.238.94 port 59546 ssh2 ... |
2019-09-24 16:43:51 |
222.190.132.82 | attackbotsspam | Sep 24 08:53:10 vps01 sshd[16564]: Failed password for root from 222.190.132.82 port 59952 ssh2 |
2019-09-24 17:18:58 |
171.249.135.114 | attackbotsspam | Connection by 171.249.135.114 on port: 139 got caught by honeypot at 9/23/2019 8:52:32 PM |
2019-09-24 16:42:20 |
200.61.249.180 | attackspambots | Sep 24 07:23:44 xxx sshd[27755]: Invalid user lihui from 200.61.249.180 Sep 24 07:23:46 xxx sshd[27755]: Failed password for invalid user lihui from 200.61.249.180 port 45888 ssh2 Sep 24 07:48:03 xxx sshd[29398]: Invalid user oper from 200.61.249.180 Sep 24 07:48:05 xxx sshd[29398]: Failed password for invalid user oper from 200.61.249.180 port 42396 ssh2 Sep 24 07:53:01 xxx sshd[29638]: Invalid user gabriel from 200.61.249.180 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=200.61.249.180 |
2019-09-24 17:17:00 |
81.22.45.25 | attack | Sep 24 10:41:46 lumpi kernel: INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.25 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=52820 PROTO=TCP SPT=55292 DPT=7006 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2019-09-24 16:51:01 |
139.217.102.155 | attack | Sep 24 04:48:27 ws12vmsma01 sshd[43746]: Invalid user ftp from 139.217.102.155 Sep 24 04:48:29 ws12vmsma01 sshd[43746]: Failed password for invalid user ftp from 139.217.102.155 port 31956 ssh2 Sep 24 04:53:33 ws12vmsma01 sshd[44455]: Invalid user prueba from 139.217.102.155 ... |
2019-09-24 16:51:25 |
52.83.98.132 | attack | 2019-09-24T08:35:48.012649abusebot-5.cloudsearch.cf sshd\[4226\]: Invalid user albtentac from 52.83.98.132 port 59322 |
2019-09-24 16:52:40 |
218.92.0.187 | attack | Sep 24 10:02:15 MK-Soft-Root2 sshd[23334]: Failed password for root from 218.92.0.187 port 1807 ssh2 Sep 24 10:02:20 MK-Soft-Root2 sshd[23334]: Failed password for root from 218.92.0.187 port 1807 ssh2 ... |
2019-09-24 17:09:00 |
192.144.142.72 | attackspam | Sep 23 20:42:52 web1 sshd\[532\]: Invalid user tunnel from 192.144.142.72 Sep 23 20:42:52 web1 sshd\[532\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.142.72 Sep 23 20:42:53 web1 sshd\[532\]: Failed password for invalid user tunnel from 192.144.142.72 port 54990 ssh2 Sep 23 20:46:52 web1 sshd\[897\]: Invalid user light from 192.144.142.72 Sep 23 20:46:52 web1 sshd\[897\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.142.72 |
2019-09-24 17:18:09 |