City: unknown
Region: unknown
Country: Egypt
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 156.197.135.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64394
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;156.197.135.42. IN A
;; AUTHORITY SECTION:
. 494 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022020700 1800 900 604800 86400
;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 22:00:38 CST 2022
;; MSG SIZE rcvd: 10742.135.197.156.in-addr.arpa domain name pointer host-156.197.42.135-static.tedata.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
42.135.197.156.in-addr.arpa name = host-156.197.42.135-static.tedata.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 219.135.209.164 | attackspam | Lines containing failures of 219.135.209.164 Aug 13 19:21:36 linuxrulz sshd[4006]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.135.209.164 user=r.r Aug 13 19:21:37 linuxrulz sshd[4006]: Failed password for r.r from 219.135.209.164 port 50633 ssh2 Aug 13 19:21:38 linuxrulz sshd[4006]: Received disconnect from 219.135.209.164 port 50633:11: Bye Bye [preauth] Aug 13 19:21:38 linuxrulz sshd[4006]: Disconnected from authenticating user r.r 219.135.209.164 port 50633 [preauth] Aug 13 19:36:59 linuxrulz sshd[5812]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.135.209.164 user=r.r Aug 13 19:37:02 linuxrulz sshd[5812]: Failed password for r.r from 219.135.209.164 port 62514 ssh2 Aug 13 19:37:03 linuxrulz sshd[5812]: Received disconnect from 219.135.209.164 port 62514:11: Bye Bye [preauth] Aug 13 19:37:03 linuxrulz sshd[5812]: Disconnected from authenticating user r.r 219.135.209.164 p........ ------------------------------ |
2020-08-15 14:35:51 |
| 222.186.180.223 | attackspam | Aug 15 08:41:36 nextcloud sshd\[10405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223 user=root Aug 15 08:41:39 nextcloud sshd\[10405\]: Failed password for root from 222.186.180.223 port 40120 ssh2 Aug 15 08:42:00 nextcloud sshd\[10947\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223 user=root |
2020-08-15 14:44:22 |
| 122.51.225.107 | attack | frenzy |
2020-08-15 14:25:02 |
| 174.21.138.106 | attack | Port 22 Scan, PTR: None |
2020-08-15 14:34:37 |
| 111.229.48.141 | attackbots | $f2bV_matches |
2020-08-15 14:25:20 |
| 218.92.0.148 | attack | Aug 14 23:38:31 dignus sshd[24910]: Failed password for root from 218.92.0.148 port 58601 ssh2 Aug 14 23:38:34 dignus sshd[24910]: Failed password for root from 218.92.0.148 port 58601 ssh2 Aug 14 23:38:37 dignus sshd[24910]: Failed password for root from 218.92.0.148 port 58601 ssh2 Aug 14 23:38:40 dignus sshd[24930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.148 user=root Aug 14 23:38:41 dignus sshd[24930]: Failed password for root from 218.92.0.148 port 36169 ssh2 ... |
2020-08-15 14:40:11 |
| 106.12.173.149 | attackspambots | frenzy |
2020-08-15 14:26:15 |
| 87.103.126.98 | attackspambots | Banned for a week because repeated abuses, for example SSH, but not only |
2020-08-15 14:10:10 |
| 118.25.91.168 | attackspambots | Failed password for root from 118.25.91.168 port 49086 ssh2 |
2020-08-15 14:08:28 |
| 45.32.216.101 | attackspam | 22/tcp [2020-08-15]1pkt |
2020-08-15 14:37:54 |
| 194.180.224.103 | attackspam | Aug 15 07:58:48 vpn01 sshd[4166]: Failed password for root from 194.180.224.103 port 34786 ssh2 ... |
2020-08-15 14:21:27 |
| 94.102.49.159 | attackbots | Aug 15 08:05:44 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=41383 PROTO=TCP SPT=45696 DPT=22092 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:10:49 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=10752 PROTO=TCP SPT=45696 DPT=23476 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:16:24 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=52777 PROTO=TCP SPT=45696 DPT=22157 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:20:06 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=6156 PROTO=TCP SPT=45696 DPT=22139 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:22:54 * ... |
2020-08-15 14:33:48 |
| 223.113.74.54 | attack | 2020-08-15T05:10:12.689182shield sshd\[15277\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.113.74.54 user=root 2020-08-15T05:10:14.951477shield sshd\[15277\]: Failed password for root from 223.113.74.54 port 52844 ssh2 2020-08-15T05:11:29.569045shield sshd\[15372\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.113.74.54 user=root 2020-08-15T05:11:31.068560shield sshd\[15372\]: Failed password for root from 223.113.74.54 port 48482 ssh2 2020-08-15T05:12:51.114405shield sshd\[15511\]: Invalid user cn from 223.113.74.54 port 45652 |
2020-08-15 14:39:47 |
| 23.94.17.223 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at hughesfamilychiro.com. - They hang out for a minute to check it out. “I’m interested… but… maybe…” - And then they hit the back button and check out the other search results instead. - Bottom line – you got an eyeball, but nothing else to show for it. - There they go. This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace. But you CAN fix that. Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site. CLICK HERE http://www.talkwithwebvisitors.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works. Time is money when it comes to connecting with lea |
2020-08-15 14:29:18 |
| 51.178.41.60 | attackspambots | frenzy |
2020-08-15 14:13:50 |