City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 98.2.19.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35579
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;98.2.19.242. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020901 1800 900 604800 86400
;; Query time: 267 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 04:26:49 CST 2025
;; MSG SIZE rcvd: 104242.19.2.98.in-addr.arpa domain name pointer syn-098-002-019-242.res.spectrum.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
242.19.2.98.in-addr.arpa name = syn-098-002-019-242.res.spectrum.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 222.186.52.39 | attackbotsspam | 13.05.2020 08:35:11 SSH access blocked by firewall |
2020-05-13 16:36:53 |
| 27.66.190.202 | attack | Port probing on unauthorized port 23 |
2020-05-13 16:22:30 |
| 162.243.143.142 | attack | 05/12/2020-23:54:07.023361 162.243.143.142 Protocol: 6 ET SCAN Suspicious inbound to mySQL port 3306 |
2020-05-13 16:44:29 |
| 217.111.155.90 | attackspambots | 217.111.155.90 - - [13/May/2020:05:54:38 +0200] "POST /wp-login.php HTTP/1.1" 200 3406 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 217.111.155.90 - - [13/May/2020:05:54:38 +0200] "POST /wp-login.php HTTP/1.1" 200 3382 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-05-13 16:19:35 |
| 134.209.236.191 | attackspam | May 13 17:44:19 web1 sshd[24947]: Invalid user wartung from 134.209.236.191 port 35934 May 13 17:44:19 web1 sshd[24947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.236.191 May 13 17:44:19 web1 sshd[24947]: Invalid user wartung from 134.209.236.191 port 35934 May 13 17:44:21 web1 sshd[24947]: Failed password for invalid user wartung from 134.209.236.191 port 35934 ssh2 May 13 17:52:03 web1 sshd[26825]: Invalid user gast from 134.209.236.191 port 35196 May 13 17:52:03 web1 sshd[26825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.236.191 May 13 17:52:03 web1 sshd[26825]: Invalid user gast from 134.209.236.191 port 35196 May 13 17:52:05 web1 sshd[26825]: Failed password for invalid user gast from 134.209.236.191 port 35196 ssh2 May 13 17:57:13 web1 sshd[28121]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.236.191 user=mysql May 13 17:5 ... |
2020-05-13 16:50:18 |
| 103.129.220.40 | attackbotsspam | Invalid user root3 from 103.129.220.40 port 53538 |
2020-05-13 16:10:08 |
| 94.177.246.39 | attackbots | May 13 04:08:28 localhost sshd\[17624\]: Invalid user masterkey from 94.177.246.39 port 36634 May 13 04:08:28 localhost sshd\[17624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.246.39 May 13 04:08:30 localhost sshd\[17624\]: Failed password for invalid user masterkey from 94.177.246.39 port 36634 ssh2 ... |
2020-05-13 16:42:19 |
| 1.53.204.14 | attack | SSH bruteforce more then 50 syn to 22 port per 10 seconds. |
2020-05-13 16:31:29 |
| 110.136.55.99 | attackspam | 20/5/12@23:54:26: FAIL: Alarm-Network address from=110.136.55.99 20/5/12@23:54:26: FAIL: Alarm-Network address from=110.136.55.99 ... |
2020-05-13 16:24:29 |
| 79.249.254.46 | attack | May 13 05:46:44 Server1 sshd[16257]: Invalid user pi from 79.249.254.46 port 34090 May 13 05:46:44 Server1 sshd[16257]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.249.254.46 May 13 05:46:44 Server1 sshd[16259]: Invalid user pi from 79.249.254.46 port 34092 May 13 05:46:44 Server1 sshd[16259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.249.254.46 May 13 05:46:46 Server1 sshd[16257]: Failed password for invalid user pi from 79.249.254.46 port 34090 ssh2 May 13 05:46:46 Server1 sshd[16257]: Connection closed by invalid user pi 79.249.254.46 port 34090 [preauth] May 13 05:46:46 Server1 sshd[16259]: Failed password for invalid user pi from 79.249.254.46 port 34092 ssh2 May 13 05:46:46 Server1 sshd[16259]: Connection closed by invalid user pi 79.249.254.46 port 34092 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=79.249.254.46 |
2020-05-13 16:43:55 |
| 117.48.208.71 | attackbotsspam | "fail2ban match" |
2020-05-13 16:45:56 |
| 192.144.230.158 | attackbotsspam | DATE:2020-05-13 10:46:36, IP:192.144.230.158, PORT:ssh SSH brute force auth (docker-dc) |
2020-05-13 16:55:46 |
| 113.184.26.6 | attackbotsspam | 20/5/12@23:54:11: FAIL: IoT-SSH address from=113.184.26.6 ... |
2020-05-13 16:39:24 |
| 103.28.52.84 | attack | May 13 02:51:48 NPSTNNYC01T sshd[20432]: Failed password for root from 103.28.52.84 port 32812 ssh2 May 13 02:55:44 NPSTNNYC01T sshd[20711]: Failed password for root from 103.28.52.84 port 36016 ssh2 ... |
2020-05-13 16:47:08 |
| 51.83.68.213 | attackspam | (sshd) Failed SSH login from 51.83.68.213 (FR/France/213.ip-51-83-68.eu): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May 13 09:24:52 amsweb01 sshd[20117]: Invalid user jaimito from 51.83.68.213 port 34632 May 13 09:24:54 amsweb01 sshd[20117]: Failed password for invalid user jaimito from 51.83.68.213 port 34632 ssh2 May 13 09:27:44 amsweb01 sshd[20371]: Invalid user viktor from 51.83.68.213 port 44310 May 13 09:27:46 amsweb01 sshd[20371]: Failed password for invalid user viktor from 51.83.68.213 port 44310 ssh2 May 13 09:29:30 amsweb01 sshd[20564]: Invalid user testftp from 51.83.68.213 port 44378 |
2020-05-13 16:13:51 |