City: unknown
Region: unknown
Country: Poland
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 94.40.45.28
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4940
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;94.40.45.28. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022020701 1800 900 604800 86400
;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 02:25:43 CST 2022
;; MSG SIZE rcvd: 10428.45.40.94.in-addr.arpa domain name pointer 94-40-45-28.tktelekom.pl.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
28.45.40.94.in-addr.arpa name = 94-40-45-28.tktelekom.pl.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 80.69.222.76 | attackbotsspam | Unauthorized IMAP connection attempt |
2020-08-08 17:31:18 |
| 118.24.2.141 | attackspambots | Aug 8 06:23:20 rocket sshd[29630]: Failed password for root from 118.24.2.141 port 58512 ssh2 Aug 8 06:28:11 rocket sshd[30477]: Failed password for root from 118.24.2.141 port 50146 ssh2 ... |
2020-08-08 17:53:59 |
| 192.99.34.42 | attack | 192.99.34.42 - - [08/Aug/2020:10:29:37 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36" 192.99.34.42 - - [08/Aug/2020:10:31:08 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36" 192.99.34.42 - - [08/Aug/2020:10:32:31 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36" ... |
2020-08-08 17:36:09 |
| 183.63.157.138 | attackspam | Cowrie Honeypot: 3 unauthorised SSH/Telnet login attempts between 2020-08-08T03:41:25Z and 2020-08-08T03:53:28Z |
2020-08-08 17:17:04 |
| 139.59.211.245 | attackbots | 2020-08-08T05:31:19.239393ns386461 sshd\[5799\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.211.245 user=root 2020-08-08T05:31:21.498539ns386461 sshd\[5799\]: Failed password for root from 139.59.211.245 port 39116 ssh2 2020-08-08T05:43:34.794550ns386461 sshd\[16402\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.211.245 user=root 2020-08-08T05:43:36.288399ns386461 sshd\[16402\]: Failed password for root from 139.59.211.245 port 40886 ssh2 2020-08-08T05:53:04.061468ns386461 sshd\[25563\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.211.245 user=root ... |
2020-08-08 17:36:49 |
| 94.28.122.140 | attackspam | 20/8/7@23:53:15: FAIL: IoT-Telnet address from=94.28.122.140 ... |
2020-08-08 17:29:58 |
| 212.19.99.12 | attack | 212.19.99.12 - - [08/Aug/2020:09:35:46 +0100] "POST /wp-login.php HTTP/1.1" 200 2435 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 212.19.99.12 - - [08/Aug/2020:09:35:47 +0100] "POST /wp-login.php HTTP/1.1" 200 2415 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 212.19.99.12 - - [08/Aug/2020:09:35:48 +0100] "POST /wp-login.php HTTP/1.1" 200 2415 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-08-08 17:37:33 |
| 104.227.121.224 | attackbotsspam | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with andoverspinecenter.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture |
2020-08-08 17:30:37 |
| 122.152.196.222 | attackspam | SSH Brute Force |
2020-08-08 17:39:12 |
| 195.54.160.38 | attackspambots | Aug 8 11:09:33 debian-2gb-nbg1-2 kernel: \[19136220.548179\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=195.54.160.38 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=51701 PROTO=TCP SPT=49673 DPT=21625 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-08-08 17:18:12 |
| 106.53.220.175 | attack | Aug 8 09:31:51 ip-172-31-61-156 sshd[7680]: Failed password for root from 106.53.220.175 port 39902 ssh2 Aug 8 09:35:45 ip-172-31-61-156 sshd[7857]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.220.175 user=root Aug 8 09:35:47 ip-172-31-61-156 sshd[7857]: Failed password for root from 106.53.220.175 port 34446 ssh2 Aug 8 09:39:38 ip-172-31-61-156 sshd[8217]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.220.175 user=root Aug 8 09:39:40 ip-172-31-61-156 sshd[8217]: Failed password for root from 106.53.220.175 port 57224 ssh2 ... |
2020-08-08 17:54:51 |
| 103.60.199.66 | attackbots | Unauthorized IMAP connection attempt |
2020-08-08 17:45:47 |
| 51.75.207.61 | attack | Aug 8 05:53:29 fhem-rasp sshd[4333]: Failed password for root from 51.75.207.61 port 51486 ssh2 Aug 8 05:53:30 fhem-rasp sshd[4333]: Disconnected from authenticating user root 51.75.207.61 port 51486 [preauth] ... |
2020-08-08 17:15:38 |
| 111.73.46.184 | attackspam |
|
2020-08-08 17:40:24 |
| 218.92.0.148 | attackspam | Unauthorized connection attempt detected from IP address 218.92.0.148 to port 22 |
2020-08-08 17:39:43 |