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 <<>> 99.2.20.69
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9998
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;99.2.20.69. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021401 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 13:41:32 CST 2025
;; MSG SIZE rcvd: 10369.20.2.99.in-addr.arpa domain name pointer 99-2-20-69.lightspeed.snantx.sbcglobal.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
69.20.2.99.in-addr.arpa name = 99-2-20-69.lightspeed.snantx.sbcglobal.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 221.125.165.59 | attack | 2020-02-09T00:42:48.164061abusebot-2.cloudsearch.cf sshd[27032]: Invalid user mim from 221.125.165.59 port 51198 2020-02-09T00:42:48.170228abusebot-2.cloudsearch.cf sshd[27032]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.125.165.59 2020-02-09T00:42:48.164061abusebot-2.cloudsearch.cf sshd[27032]: Invalid user mim from 221.125.165.59 port 51198 2020-02-09T00:42:50.748501abusebot-2.cloudsearch.cf sshd[27032]: Failed password for invalid user mim from 221.125.165.59 port 51198 ssh2 2020-02-09T00:46:44.393835abusebot-2.cloudsearch.cf sshd[27270]: Invalid user ax from 221.125.165.59 port 56854 2020-02-09T00:46:44.399333abusebot-2.cloudsearch.cf sshd[27270]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.125.165.59 2020-02-09T00:46:44.393835abusebot-2.cloudsearch.cf sshd[27270]: Invalid user ax from 221.125.165.59 port 56854 2020-02-09T00:46:45.708146abusebot-2.cloudsearch.cf sshd[27270]: Failed pass ... |
2020-02-09 09:48:58 |
| 43.245.185.71 | attackspambots | Feb 9 01:12:37 web8 sshd\[7178\]: Invalid user mkp from 43.245.185.71 Feb 9 01:12:37 web8 sshd\[7178\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.245.185.71 Feb 9 01:12:38 web8 sshd\[7178\]: Failed password for invalid user mkp from 43.245.185.71 port 47698 ssh2 Feb 9 01:15:31 web8 sshd\[8609\]: Invalid user dzd from 43.245.185.71 Feb 9 01:15:31 web8 sshd\[8609\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.245.185.71 |
2020-02-09 09:51:22 |
| 192.241.234.109 | attackspam | Lines containing failures of 192.241.234.109 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=192.241.234.109 |
2020-02-09 10:17:44 |
| 77.247.110.15 | attackspambots | 77.247.110.15 was recorded 10 times by 7 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 10, 10, 167 |
2020-02-09 09:46:18 |
| 222.186.30.57 | attack | Feb 9 03:25:21 MK-Soft-Root1 sshd[12329]: Failed password for root from 222.186.30.57 port 38581 ssh2 Feb 9 03:25:25 MK-Soft-Root1 sshd[12329]: Failed password for root from 222.186.30.57 port 38581 ssh2 ... |
2020-02-09 10:28:58 |
| 120.52.120.18 | attackbotsspam | Feb 9 02:14:59 srv01 sshd[7904]: Invalid user rvy from 120.52.120.18 port 54100 Feb 9 02:14:59 srv01 sshd[7904]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.52.120.18 Feb 9 02:14:59 srv01 sshd[7904]: Invalid user rvy from 120.52.120.18 port 54100 Feb 9 02:15:01 srv01 sshd[7904]: Failed password for invalid user rvy from 120.52.120.18 port 54100 ssh2 Feb 9 02:18:10 srv01 sshd[8103]: Invalid user buu from 120.52.120.18 port 34114 ... |
2020-02-09 09:58:58 |
| 178.128.30.243 | attack | Feb 9 01:55:32 pi sshd[7401]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.30.243 Feb 9 01:55:34 pi sshd[7401]: Failed password for invalid user rxd from 178.128.30.243 port 42868 ssh2 |
2020-02-09 10:01:21 |
| 52.34.83.11 | attack | 02/09/2020-03:19:48.676280 52.34.83.11 Protocol: 6 SURICATA TLS invalid record/traffic |
2020-02-09 10:19:57 |
| 163.172.122.165 | attack | Feb 9 02:47:07 MK-Soft-Root2 sshd[11598]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.122.165 Feb 9 02:47:09 MK-Soft-Root2 sshd[11598]: Failed password for invalid user myl from 163.172.122.165 port 54006 ssh2 ... |
2020-02-09 10:20:47 |
| 46.101.19.133 | attackspam | Lines containing failures of 46.101.19.133 Feb 3 09:31:09 shared09 sshd[16661]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.19.133 user=r.r Feb 3 09:31:12 shared09 sshd[16661]: Failed password for r.r from 46.101.19.133 port 46684 ssh2 Feb 3 09:31:12 shared09 sshd[16661]: Received disconnect from 46.101.19.133 port 46684:11: Bye Bye [preauth] Feb 3 09:31:12 shared09 sshd[16661]: Disconnected from authenticating user r.r 46.101.19.133 port 46684 [preauth] Feb 3 09:51:00 shared09 sshd[23032]: Invalid user jira from 46.101.19.133 port 45390 Feb 3 09:51:00 shared09 sshd[23032]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.19.133 Feb 3 09:51:03 shared09 sshd[23032]: Failed password for invalid user jira from 46.101.19.133 port 45390 ssh2 Feb 3 09:51:03 shared09 sshd[23032]: Received disconnect from 46.101.19.133 port 45390:11: Bye Bye [preauth] Feb 3 09:51:03 shared0........ ------------------------------ |
2020-02-09 10:15:56 |
| 139.59.190.69 | attackbots | Feb 8 21:46:11 ws22vmsma01 sshd[240264]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.190.69 Feb 8 21:46:13 ws22vmsma01 sshd[240264]: Failed password for invalid user xcx from 139.59.190.69 port 58653 ssh2 ... |
2020-02-09 10:01:36 |
| 211.252.87.90 | attackbots | Feb 8 22:47:27 firewall sshd[19489]: Invalid user sri from 211.252.87.90 Feb 8 22:47:29 firewall sshd[19489]: Failed password for invalid user sri from 211.252.87.90 port 18445 ssh2 Feb 8 22:50:57 firewall sshd[19715]: Invalid user frh from 211.252.87.90 ... |
2020-02-09 10:19:35 |
| 60.190.129.6 | attackbots | Feb 2 23:19:40 sanyalnet-awsem3-1 sshd[2184]: Connection from 60.190.129.6 port 50760 on 172.30.0.184 port 22 Feb 2 23:19:41 sanyalnet-awsem3-1 sshd[2184]: reveeclipse mapping checking getaddrinfo for mail.jecjk.com [60.190.129.6] failed - POSSIBLE BREAK-IN ATTEMPT! Feb 2 23:19:41 sanyalnet-awsem3-1 sshd[2184]: Invalid user oracle from 60.190.129.6 Feb 2 23:19:42 sanyalnet-awsem3-1 sshd[2184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.190.129.6 Feb 2 23:19:43 sanyalnet-awsem3-1 sshd[2184]: Failed password for invalid user oracle from 60.190.129.6 port 50760 ssh2 Feb 2 23:19:44 sanyalnet-awsem3-1 sshd[2184]: Received disconnect from 60.190.129.6: 11: Normal Shutdown [preauth] Feb 2 23:39:09 sanyalnet-awsem3-1 sshd[3181]: Connection from 60.190.129.6 port 43158 on 172.30.0.184 port 22 Feb 2 23:39:16 sanyalnet-awsem3-1 sshd[3181]: reveeclipse mapping checking getaddrinfo for mail.jecjk.com [60.190.129.6] failed - PO........ ------------------------------- |
2020-02-09 10:18:48 |
| 117.107.133.162 | attackspam | 2020-02-08T20:32:10.676632vostok sshd\[29771\]: Invalid user tr from 117.107.133.162 port 34074 | Triggered by Fail2Ban at Vostok web server |
2020-02-09 10:13:15 |
| 66.70.142.211 | attack | Feb 9 01:27:01 icinga sshd[26824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.142.211 Feb 9 01:27:03 icinga sshd[26824]: Failed password for invalid user osn from 66.70.142.211 port 47390 ssh2 Feb 9 01:46:49 icinga sshd[45987]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.142.211 ... |
2020-02-09 09:46:35 |