City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 64.64.143.54
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20983
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;64.64.143.54. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020600 1800 900 604800 86400
;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 20:06:43 CST 2025
;; MSG SIZE rcvd: 10554.143.64.64.in-addr.arpa domain name pointer gpc-64-64-143-54-ne.gpcom.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
54.143.64.64.in-addr.arpa name = gpc-64-64-143-54-ne.gpcom.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 122.199.225.53 | attackbots | Jul 15 04:33:19 home sshd[13562]: Invalid user web from 122.199.225.53 port 41146 Jul 15 04:33:19 home sshd[13562]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.199.225.53 Jul 15 04:33:19 home sshd[13562]: Invalid user web from 122.199.225.53 port 41146 Jul 15 04:33:22 home sshd[13562]: Failed password for invalid user web from 122.199.225.53 port 41146 ssh2 Jul 15 04:43:34 home sshd[13709]: Invalid user proftpd from 122.199.225.53 port 60930 Jul 15 04:43:34 home sshd[13709]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.199.225.53 Jul 15 04:43:34 home sshd[13709]: Invalid user proftpd from 122.199.225.53 port 60930 Jul 15 04:43:36 home sshd[13709]: Failed password for invalid user proftpd from 122.199.225.53 port 60930 ssh2 Jul 15 04:49:19 home sshd[13832]: Invalid user dimitri from 122.199.225.53 port 59786 Jul 15 04:49:19 home sshd[13832]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh r |
2019-07-15 21:53:42 |
| 139.59.94.192 | attackspambots | Automatic report - Banned IP Access |
2019-07-15 22:12:09 |
| 62.210.91.100 | attack | 2019-07-15T14:46:44.946789enmeeting.mahidol.ac.th sshd\[10773\]: User root from 62-210-91-100.rev.poneytelecom.eu not allowed because not listed in AllowUsers 2019-07-15T14:46:45.084096enmeeting.mahidol.ac.th sshd\[10773\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62-210-91-100.rev.poneytelecom.eu user=root 2019-07-15T14:46:46.607465enmeeting.mahidol.ac.th sshd\[10773\]: Failed password for invalid user root from 62.210.91.100 port 52631 ssh2 ... |
2019-07-15 21:55:59 |
| 59.125.214.115 | attackspam | Automatic report - Banned IP Access |
2019-07-15 22:30:49 |
| 198.176.48.192 | attackbotsspam | SSH Brute Force, server-1 sshd[8370]: Failed password for root from 198.176.48.192 port 64148 ssh2 |
2019-07-15 22:06:17 |
| 173.212.225.24 | attackspambots | WordPress wp-login brute force :: 173.212.225.24 0.064 BYPASS [15/Jul/2019:16:18:42 1000] [censored_4] "POST /wp-login.php HTTP/1.1" 200 4214 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2019-07-15 22:23:49 |
| 109.130.118.228 | attackbots | Honeypot attack, port: 23, PTR: 228.118-130-109.adsl-dyn.isp.belgacom.be. |
2019-07-15 22:42:18 |
| 81.26.66.36 | attack | Jul 15 12:31:05 [munged] sshd[2987]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.26.66.36 |
2019-07-15 22:41:37 |
| 167.99.3.40 | attackspam | Jul 15 14:47:02 v22019058497090703 sshd[17222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.3.40 Jul 15 14:47:05 v22019058497090703 sshd[17222]: Failed password for invalid user dasusr1 from 167.99.3.40 port 51559 ssh2 Jul 15 14:51:32 v22019058497090703 sshd[17502]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.3.40 ... |
2019-07-15 21:52:51 |
| 130.211.96.77 | attackbotsspam | Fail2Ban Ban Triggered |
2019-07-15 21:51:17 |
| 138.68.94.173 | attack | Multiple SSH auth failures recorded by fail2ban |
2019-07-15 21:50:55 |
| 185.73.245.212 | attack | Invalid user freak from 185.73.245.212 port 49006 |
2019-07-15 21:43:21 |
| 45.55.158.8 | attackspam | Jul 15 10:31:01 sshgateway sshd\[4813\]: Invalid user public from 45.55.158.8 Jul 15 10:31:01 sshgateway sshd\[4813\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.158.8 Jul 15 10:31:02 sshgateway sshd\[4813\]: Failed password for invalid user public from 45.55.158.8 port 44008 ssh2 |
2019-07-15 21:45:00 |
| 139.99.9.2 | attack | 190 attacks over the last 10 minutes. Below is a sample of these recent attacks: July 15, 2019 1:21am 139.99.9.2 (Singapore) Blocked for Newspaper Premium Theme <= 6.7.1 - Privilege Escalation July 15, 2019 1:21am 139.99.9.2 (Singapore) Blocked for Yellow Pencil Visual Theme Customizer <= 7.1.9 Arbitrary Options Update in query string: yp_remote_get=test July 15, 2019 1:21am 139.99.9.2 (Singapore) Blocked for Yellow Pencil Visual Theme Customizer <= 7.1.9 Arbitrary Options Update in query string: yp_remote_get=test July 15, 2019 1:21am 139.99.9.2 (Singapore) Blocked for WP GDPR Compliance <= 1.4.2 - Update Any Option / Call Any Action in POST body: action=wpgdprc_process_action |
2019-07-15 22:00:37 |
| 221.149.76.68 | attackbotsspam | Invalid user mj from 221.149.76.68 port 59117 |
2019-07-15 22:24:26 |