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.45.44.54
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10479
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;99.45.44.54. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021301 1800 900 604800 86400
;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 04:04:15 CST 2025
;; MSG SIZE rcvd: 104
54.44.45.99.in-addr.arpa domain name pointer 99-45-44-54.lightspeed.wlfrct.sbcglobal.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
54.44.45.99.in-addr.arpa name = 99-45-44-54.lightspeed.wlfrct.sbcglobal.net.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 51.91.157.167 | attackbotsspam | Oct 31 22:15:55 taivassalofi sshd[235755]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.157.167 Oct 31 22:15:57 taivassalofi sshd[235755]: Failed password for invalid user COM from 51.91.157.167 port 38816 ssh2 ... |
2019-11-01 04:24:22 |
| 104.248.159.69 | attackbots | 2019-10-31 01:32:36,119 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 01:49:20,886 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 02:10:32,827 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 02:27:38,930 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 02:44:57,546 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 01:32:36,119 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 01:49:20,886 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 02:10:32,827 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 02:27:38,930 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 02:44:57,546 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2019-10-31 01:32:36,119 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 104.248.159.69 2 |
2019-11-01 04:15:06 |
| 103.109.108.50 | attackbotsspam | Unauthorized IMAP connection attempt |
2019-11-01 04:48:36 |
| 221.162.255.78 | attackspam | Oct 31 21:15:32 MK-Soft-VM4 sshd[9997]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.162.255.78 Oct 31 21:15:34 MK-Soft-VM4 sshd[9997]: Failed password for invalid user ny from 221.162.255.78 port 51798 ssh2 ... |
2019-11-01 04:42:27 |
| 59.115.161.106 | attack | Scanning random ports - tries to find possible vulnerable services |
2019-11-01 04:37:20 |
| 177.73.231.68 | attackbots | Unauthorized connection attempt from IP address 177.73.231.68 on Port 445(SMB) |
2019-11-01 04:49:33 |
| 50.2.189.106 | attackbotsspam | 2019-10-31T20:15:46.414688abusebot-6.cloudsearch.cf sshd\[2642\]: Invalid user info from 50.2.189.106 port 52642 |
2019-11-01 04:35:55 |
| 222.186.180.223 | attackbots | Oct 31 21:52:26 dcd-gentoo sshd[19844]: User root from 222.186.180.223 not allowed because none of user's groups are listed in AllowGroups Oct 31 21:52:31 dcd-gentoo sshd[19844]: error: PAM: Authentication failure for illegal user root from 222.186.180.223 Oct 31 21:52:26 dcd-gentoo sshd[19844]: User root from 222.186.180.223 not allowed because none of user's groups are listed in AllowGroups Oct 31 21:52:31 dcd-gentoo sshd[19844]: error: PAM: Authentication failure for illegal user root from 222.186.180.223 Oct 31 21:52:26 dcd-gentoo sshd[19844]: User root from 222.186.180.223 not allowed because none of user's groups are listed in AllowGroups Oct 31 21:52:31 dcd-gentoo sshd[19844]: error: PAM: Authentication failure for illegal user root from 222.186.180.223 Oct 31 21:52:31 dcd-gentoo sshd[19844]: Failed keyboard-interactive/pam for invalid user root from 222.186.180.223 port 49884 ssh2 ... |
2019-11-01 04:53:06 |
| 104.202.4.222 | attackbotsspam | Registration form abuse |
2019-11-01 04:20:35 |
| 119.123.101.144 | attackspam | Oct 31 20:12:27 ip-172-31-1-72 sshd\[18317\]: Invalid user bd from 119.123.101.144 Oct 31 20:12:27 ip-172-31-1-72 sshd\[18317\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.101.144 Oct 31 20:12:30 ip-172-31-1-72 sshd\[18317\]: Failed password for invalid user bd from 119.123.101.144 port 37728 ssh2 Oct 31 20:15:55 ip-172-31-1-72 sshd\[18367\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.101.144 user=root Oct 31 20:15:57 ip-172-31-1-72 sshd\[18367\]: Failed password for root from 119.123.101.144 port 45034 ssh2 |
2019-11-01 04:20:04 |
| 123.138.18.35 | attackspam | Oct 31 22:55:50 hosting sshd[26404]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.138.18.35 user=root Oct 31 22:55:52 hosting sshd[26404]: Failed password for root from 123.138.18.35 port 41892 ssh2 Oct 31 23:11:32 hosting sshd[27479]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.138.18.35 user=root Oct 31 23:11:34 hosting sshd[27479]: Failed password for root from 123.138.18.35 port 43577 ssh2 Oct 31 23:15:50 hosting sshd[27767]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.138.18.35 user=root Oct 31 23:15:52 hosting sshd[27767]: Failed password for root from 123.138.18.35 port 33977 ssh2 ... |
2019-11-01 04:28:11 |
| 119.46.90.137 | attack | Oct 31 20:11:46 localhost sshd\[66703\]: Invalid user teamspeak3 from 119.46.90.137 port 40724 Oct 31 20:11:46 localhost sshd\[66703\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.46.90.137 Oct 31 20:11:48 localhost sshd\[66703\]: Failed password for invalid user teamspeak3 from 119.46.90.137 port 40724 ssh2 Oct 31 20:15:44 localhost sshd\[66813\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.46.90.137 user=root Oct 31 20:15:46 localhost sshd\[66813\]: Failed password for root from 119.46.90.137 port 48662 ssh2 ... |
2019-11-01 04:35:12 |
| 180.253.88.209 | attack | Unauthorized connection attempt from IP address 180.253.88.209 on Port 445(SMB) |
2019-11-01 04:30:03 |
| 23.251.142.181 | attackbots | Oct 31 21:12:08 sd-53420 sshd\[1894\]: Invalid user proteu from 23.251.142.181 Oct 31 21:12:08 sd-53420 sshd\[1894\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.251.142.181 Oct 31 21:12:10 sd-53420 sshd\[1894\]: Failed password for invalid user proteu from 23.251.142.181 port 20515 ssh2 Oct 31 21:15:49 sd-53420 sshd\[2201\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.251.142.181 user=root Oct 31 21:15:51 sd-53420 sshd\[2201\]: Failed password for root from 23.251.142.181 port 59391 ssh2 ... |
2019-11-01 04:29:47 |
| 167.71.3.163 | attack | 2019-10-31T20:15:28.988028abusebot-8.cloudsearch.cf sshd\[31343\]: Invalid user tmgvision from 167.71.3.163 port 24784 |
2019-11-01 04:47:01 |