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 <<>> 68.162.21.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54402
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;68.162.21.94. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021600 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 22:12:15 CST 2025
;; MSG SIZE rcvd: 10594.21.162.68.in-addr.arpa domain name pointer pool-68-162-21-94.nwrk.east.verizon.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
94.21.162.68.in-addr.arpa name = pool-68-162-21-94.nwrk.east.verizon.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 140.143.57.159 | attackspambots | SSH Brute Force |
2020-08-15 14:53:22 |
| 23.94.5.52 | attackspambots | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at hughesfamilychiro.com. - They hang out for a minute to check it out. “I’m interested… but… maybe…” - And then they hit the back button and check out the other search results instead. - Bottom line – you got an eyeball, but nothing else to show for it. - There they go. This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace. But you CAN fix that. Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site. CLICK HERE http://www.talkwithwebvisitors.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works. Time is money when it comes to connecting with lea |
2020-08-15 14:31:56 |
| 146.0.228.195 | attackspam |
|
2020-08-15 14:36:25 |
| 177.42.9.234 | attackbots | Aug 15 09:47:59 gw1 sshd[28705]: Failed password for root from 177.42.9.234 port 42484 ssh2 ... |
2020-08-15 14:50:09 |
| 36.84.80.31 | attackspam | Aug 15 07:06:55 server sshd[29389]: Failed password for root from 36.84.80.31 port 62273 ssh2 Aug 15 07:18:03 server sshd[33807]: Failed password for root from 36.84.80.31 port 38081 ssh2 Aug 15 07:33:31 server sshd[40525]: Failed password for root from 36.84.80.31 port 64737 ssh2 |
2020-08-15 14:17:44 |
| 218.92.0.148 | attack | Aug 14 23:38:31 dignus sshd[24910]: Failed password for root from 218.92.0.148 port 58601 ssh2 Aug 14 23:38:34 dignus sshd[24910]: Failed password for root from 218.92.0.148 port 58601 ssh2 Aug 14 23:38:37 dignus sshd[24910]: Failed password for root from 218.92.0.148 port 58601 ssh2 Aug 14 23:38:40 dignus sshd[24930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.148 user=root Aug 14 23:38:41 dignus sshd[24930]: Failed password for root from 218.92.0.148 port 36169 ssh2 ... |
2020-08-15 14:40:11 |
| 222.186.175.217 | attack | 2020-08-15T06:33:46.676241shield sshd\[22419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.217 user=root 2020-08-15T06:33:47.939376shield sshd\[22419\]: Failed password for root from 222.186.175.217 port 49976 ssh2 2020-08-15T06:33:53.056729shield sshd\[22419\]: Failed password for root from 222.186.175.217 port 49976 ssh2 2020-08-15T06:33:56.020487shield sshd\[22419\]: Failed password for root from 222.186.175.217 port 49976 ssh2 2020-08-15T06:33:59.057883shield sshd\[22419\]: Failed password for root from 222.186.175.217 port 49976 ssh2 |
2020-08-15 14:45:23 |
| 81.17.16.148 | attack | Automatic report - Banned IP Access |
2020-08-15 14:50:49 |
| 178.47.143.198 | attackbots | Aug 15 04:22:23 serwer sshd\[20990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.47.143.198 user=root Aug 15 04:22:25 serwer sshd\[20990\]: Failed password for root from 178.47.143.198 port 55004 ssh2 Aug 15 04:24:34 serwer sshd\[22217\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.47.143.198 user=root ... |
2020-08-15 14:53:07 |
| 187.162.58.117 | attackspam | Automatic report - Port Scan Attack |
2020-08-15 14:52:01 |
| 171.241.57.175 | attack | 1597463766 - 08/15/2020 05:56:06 Host: 171.241.57.175/171.241.57.175 Port: 445 TCP Blocked |
2020-08-15 14:18:07 |
| 94.102.49.190 | attackbots | Fail2Ban Ban Triggered |
2020-08-15 14:49:43 |
| 222.186.42.137 | attack | Aug 15 08:09:14 vps639187 sshd\[8343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.137 user=root Aug 15 08:09:15 vps639187 sshd\[8343\]: Failed password for root from 222.186.42.137 port 59118 ssh2 Aug 15 08:09:17 vps639187 sshd\[8343\]: Failed password for root from 222.186.42.137 port 59118 ssh2 ... |
2020-08-15 14:10:53 |
| 177.209.86.224 | attack | Automatic report - Port Scan Attack |
2020-08-15 14:27:42 |
| 218.92.0.223 | attack | Fail2Ban Ban Triggered (2) |
2020-08-15 14:28:46 |