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.18.195.153
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36359
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;99.18.195.153. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021700 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 17:29:23 CST 2025
;; MSG SIZE rcvd: 106
153.195.18.99.in-addr.arpa domain name pointer 99-18-195-153.lightspeed.hstntx.sbcglobal.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
153.195.18.99.in-addr.arpa name = 99-18-195-153.lightspeed.hstntx.sbcglobal.net.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 111.229.254.17 | attackbots | Aug 4 14:25:59 vserver sshd\[29241\]: Failed password for root from 111.229.254.17 port 58034 ssh2Aug 4 14:29:14 vserver sshd\[29293\]: Failed password for root from 111.229.254.17 port 35396 ssh2Aug 4 14:32:27 vserver sshd\[29566\]: Failed password for root from 111.229.254.17 port 40990 ssh2Aug 4 14:35:51 vserver sshd\[29613\]: Failed password for root from 111.229.254.17 port 46584 ssh2 ... |
2020-08-04 22:56:20 |
| 23.81.230.136 | attack | (From eric@talkwithwebvisitor.com) Hello, my name’s Eric and I just ran across your website at truthchiropractic.com... I found it after a quick search, so your SEO’s working out… Content looks pretty good… One thing’s missing though… A QUICK, EASY way to connect with you NOW. Because studies show that a web lead like me will only hang out a few seconds – 7 out of 10 disappear almost instantly, Surf Surf Surf… then gone forever. I have the solution: 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. You’ll know immediately they’re interested and you can call them directly to TALK with them - literally while they’re still on the web looking at 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 and even give it a try… it could be huge for your business. Plus, now that you’ve got that phone number, with our new |
2020-08-04 23:12:21 |
| 49.233.88.126 | attack | Aug 4 12:19:42 mail sshd[11242]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.88.126 user=root Aug 4 12:19:44 mail sshd[11242]: Failed password for root from 49.233.88.126 port 42412 ssh2 ... |
2020-08-04 22:54:41 |
| 157.245.255.113 | attackbots | Aug 4 12:39:08 *** sshd[13968]: User root from 157.245.255.113 not allowed because not listed in AllowUsers |
2020-08-04 23:05:27 |
| 222.82.214.218 | attack | 2020-08-04T13:46:44.340299abusebot.cloudsearch.cf sshd[26964]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.82.214.218 user=root 2020-08-04T13:46:46.233210abusebot.cloudsearch.cf sshd[26964]: Failed password for root from 222.82.214.218 port 23111 ssh2 2020-08-04T13:51:56.454829abusebot.cloudsearch.cf sshd[27026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.82.214.218 user=root 2020-08-04T13:51:58.844533abusebot.cloudsearch.cf sshd[27026]: Failed password for root from 222.82.214.218 port 23113 ssh2 2020-08-04T13:53:51.827210abusebot.cloudsearch.cf sshd[27107]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.82.214.218 user=root 2020-08-04T13:53:53.669984abusebot.cloudsearch.cf sshd[27107]: Failed password for root from 222.82.214.218 port 23114 ssh2 2020-08-04T13:55:37.849313abusebot.cloudsearch.cf sshd[27135]: pam_unix(sshd:auth): authenticatio ... |
2020-08-04 22:50:01 |
| 118.70.133.224 | attackspam | 1596532941 - 08/04/2020 11:22:21 Host: 118.70.133.224/118.70.133.224 Port: 445 TCP Blocked |
2020-08-04 23:00:43 |
| 118.25.153.63 | attackspambots | 2020-08-04T11:10:47.546077ns386461 sshd\[11312\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.153.63 user=root 2020-08-04T11:10:50.116654ns386461 sshd\[11312\]: Failed password for root from 118.25.153.63 port 47426 ssh2 2020-08-04T11:19:21.399855ns386461 sshd\[18621\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.153.63 user=root 2020-08-04T11:19:23.198492ns386461 sshd\[18621\]: Failed password for root from 118.25.153.63 port 43590 ssh2 2020-08-04T11:23:00.891134ns386461 sshd\[22056\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.153.63 user=root ... |
2020-08-04 22:29:58 |
| 81.68.105.55 | attackbots | 2020-08-04T14:00:07.935545shield sshd\[28013\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.68.105.55 user=root 2020-08-04T14:00:10.395859shield sshd\[28013\]: Failed password for root from 81.68.105.55 port 45854 ssh2 2020-08-04T14:03:43.644682shield sshd\[28361\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.68.105.55 user=root 2020-08-04T14:03:45.761842shield sshd\[28361\]: Failed password for root from 81.68.105.55 port 54544 ssh2 2020-08-04T14:07:25.292853shield sshd\[28836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.68.105.55 user=root |
2020-08-04 22:32:25 |
| 200.76.195.34 | attack | Automatic report - Port Scan Attack |
2020-08-04 22:46:26 |
| 58.246.187.102 | attack | 2020-08-04T04:22:11.512843morrigan.ad5gb.com sshd[2500433]: Failed password for root from 58.246.187.102 port 16512 ssh2 2020-08-04T04:22:12.178755morrigan.ad5gb.com sshd[2500433]: Disconnected from authenticating user root 58.246.187.102 port 16512 [preauth] |
2020-08-04 23:07:18 |
| 91.121.211.34 | attack | Banned for a week because repeated abuses, for example SSH, but not only |
2020-08-04 22:36:22 |
| 39.109.127.67 | attack | Aug 4 16:54:15 our-server-hostname sshd[16854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.109.127.67 user=r.r Aug 4 16:54:17 our-server-hostname sshd[16854]: Failed password for r.r from 39.109.127.67 port 44587 ssh2 Aug 4 17:32:09 our-server-hostname sshd[25786]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.109.127.67 user=r.r Aug 4 17:32:11 our-server-hostname sshd[25786]: Failed password for r.r from 39.109.127.67 port 53109 ssh2 Aug 4 17:36:21 our-server-hostname sshd[27019]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.109.127.67 user=r.r Aug 4 17:36:22 our-server-hostname sshd[27019]: Failed password for r.r from 39.109.127.67 port 56903 ssh2 Aug 4 17:40:30 our-server-hostname sshd[28566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.109.127.67 user=r.r Aug 4 17:40:32 ........ ------------------------------- |
2020-08-04 22:55:12 |
| 23.95.97.171 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hello, my name’s Eric and I just ran across your website at truthchiropractic.com... I found it after a quick search, so your SEO’s working out… Content looks pretty good… One thing’s missing though… A QUICK, EASY way to connect with you NOW. Because studies show that a web lead like me will only hang out a few seconds – 7 out of 10 disappear almost instantly, Surf Surf Surf… then gone forever. I have the solution: 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. You’ll know immediately they’re interested and you can call them directly to TALK with them - literally while they’re still on the web looking at 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 and even give it a try… it could be huge for your business. Plus, now that you’ve got that phone number, with our new |
2020-08-04 23:05:59 |
| 180.249.41.85 | attackspam | Automatic report - Port Scan Attack |
2020-08-04 22:51:19 |
| 178.134.87.204 | attackbots | 1596532943 - 08/04/2020 11:22:23 Host: 178.134.87.204/178.134.87.204 Port: 445 TCP Blocked |
2020-08-04 22:57:57 |