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 <<>> 166.167.242.168
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29981
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;166.167.242.168. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021401 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 06:58:39 CST 2025
;; MSG SIZE rcvd: 108168.242.167.166.in-addr.arpa domain name pointer 168.sub-166-167-242.myvzw.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
168.242.167.166.in-addr.arpa name = 168.sub-166-167-242.myvzw.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 90.48.71.99 | attackspambots | Jan 21 08:49:16 nexus sshd[17052]: Invalid user support from 90.48.71.99 port 37824 Jan 21 08:49:16 nexus sshd[17052]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.48.71.99 Jan 21 08:49:18 nexus sshd[17052]: Failed password for invalid user support from 90.48.71.99 port 37824 ssh2 Jan 21 08:49:18 nexus sshd[17052]: Received disconnect from 90.48.71.99 port 37824:11: Bye Bye [preauth] Jan 21 08:49:18 nexus sshd[17052]: Disconnected from 90.48.71.99 port 37824 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=90.48.71.99 |
2020-01-21 19:35:13 |
| 217.112.138.143 | attackbotsspam | Unauthorized connection attempt detected from IP address 217.112.138.143 to port 80 [J] |
2020-01-21 19:21:59 |
| 69.206.197.186 | attackbotsspam | Unauthorized connection attempt detected from IP address 69.206.197.186 to port 81 [J] |
2020-01-21 19:39:55 |
| 190.247.112.53 | attack | Caught in portsentry honeypot |
2020-01-21 19:50:44 |
| 109.73.88.66 | attackspambots | Unauthorized connection attempt detected from IP address 109.73.88.66 to port 81 [J] |
2020-01-21 19:33:26 |
| 141.101.229.61 | attackspam | Unauthorized connection attempt detected from IP address 141.101.229.61 to port 8080 [J] |
2020-01-21 19:30:34 |
| 185.95.186.161 | attack | Unauthorized connection attempt detected from IP address 185.95.186.161 to port 80 [J] |
2020-01-21 19:53:19 |
| 49.51.9.19 | attackspambots | Unauthorized connection attempt detected from IP address 49.51.9.19 to port 2052 [J] |
2020-01-21 19:43:01 |
| 37.191.211.98 | attackbotsspam | Unauthorized connection attempt detected from IP address 37.191.211.98 to port 23 [J] |
2020-01-21 19:45:12 |
| 220.135.33.164 | attack | Unauthorized connection attempt detected from IP address 220.135.33.164 to port 81 [J] |
2020-01-21 19:20:49 |
| 190.57.152.52 | attackbots | Unauthorized connection attempt detected from IP address 190.57.152.52 to port 23 [J] |
2020-01-21 19:52:27 |
| 193.19.119.26 | normal | so how does this work |
2020-01-21 19:19:35 |
| 206.189.183.8 | attackbotsspam | Unauthorized connection attempt detected from IP address 206.189.183.8 to port 2004 [J] |
2020-01-21 19:47:55 |
| 201.103.98.37 | attack | Unauthorized connection attempt detected from IP address 201.103.98.37 to port 88 [J] |
2020-01-21 19:48:13 |
| 191.100.10.168 | attackbotsspam | Unauthorized connection attempt detected from IP address 191.100.10.168 to port 80 [J] |
2020-01-21 19:25:01 |