城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 99.42.235.78
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11756
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;99.42.235.78. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020600 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 22:24:12 CST 2025
;; MSG SIZE rcvd: 10578.235.42.99.in-addr.arpa domain name pointer 99-42-235-78.lightspeed.mssnks.sbcglobal.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
78.235.42.99.in-addr.arpa name = 99-42-235-78.lightspeed.mssnks.sbcglobal.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 23.94.177.187 | attackbots | (From eric@talkwithcustomer.com) Hey, You have a website roscoechiro.com, right? Of course you do. I am looking at your website now. It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get. Not including all of the work you put into creating social media, videos, blog posts, emails, and so on. So you’re investing seriously in getting people to that site. But how’s it working? Great? Okay? Not so much? If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should. Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better. You could actually get up to 100X more conversions! I’m not making this up. As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes. He’s backed up by a study a |
2019-10-13 12:35:42 |
| 71.6.199.23 | attack | 13.10.2019 04:03:15 Connection to port 6881 blocked by firewall |
2019-10-13 12:07:19 |
| 222.186.180.41 | attackspam | Oct 13 06:22:32 tux-35-217 sshd\[18706\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.41 user=root Oct 13 06:22:34 tux-35-217 sshd\[18706\]: Failed password for root from 222.186.180.41 port 27946 ssh2 Oct 13 06:22:39 tux-35-217 sshd\[18706\]: Failed password for root from 222.186.180.41 port 27946 ssh2 Oct 13 06:22:43 tux-35-217 sshd\[18706\]: Failed password for root from 222.186.180.41 port 27946 ssh2 ... |
2019-10-13 12:24:05 |
| 222.186.173.142 | attack | Oct 13 06:00:38 MK-Soft-Root1 sshd[11092]: Failed password for root from 222.186.173.142 port 33130 ssh2 Oct 13 06:00:44 MK-Soft-Root1 sshd[11092]: Failed password for root from 222.186.173.142 port 33130 ssh2 ... |
2019-10-13 12:24:57 |
| 210.5.88.19 | attackspambots | Oct 13 06:57:45 www5 sshd\[9802\]: Invalid user Roman2017 from 210.5.88.19 Oct 13 06:57:45 www5 sshd\[9802\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.5.88.19 Oct 13 06:57:47 www5 sshd\[9802\]: Failed password for invalid user Roman2017 from 210.5.88.19 port 35596 ssh2 ... |
2019-10-13 12:10:15 |
| 222.186.30.152 | attackbotsspam | v+ssh-bruteforce |
2019-10-13 12:18:30 |
| 181.198.86.24 | attack | Oct 13 05:57:29 ns41 sshd[5565]: Failed password for root from 181.198.86.24 port 35861 ssh2 Oct 13 05:57:29 ns41 sshd[5565]: Failed password for root from 181.198.86.24 port 35861 ssh2 |
2019-10-13 12:25:14 |
| 35.196.35.117 | attack | Automated report (2019-10-13T00:21:55+00:00). Misbehaving bot detected at this address. |
2019-10-13 08:30:31 |
| 158.69.210.117 | attackspambots | 2019-10-13T03:57:16.174686abusebot-7.cloudsearch.cf sshd\[15493\]: Invalid user Qaz_123 from 158.69.210.117 port 41248 |
2019-10-13 12:35:04 |
| 5.39.67.154 | attackspambots | SSH Brute Force, server-1 sshd[22984]: Failed password for root from 5.39.67.154 port 35992 ssh2 |
2019-10-13 08:20:04 |
| 203.177.70.171 | attack | Oct 13 05:47:40 ncomp sshd[26415]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.177.70.171 user=root Oct 13 05:47:42 ncomp sshd[26415]: Failed password for root from 203.177.70.171 port 40806 ssh2 Oct 13 05:57:39 ncomp sshd[26531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.177.70.171 user=root Oct 13 05:57:41 ncomp sshd[26531]: Failed password for root from 203.177.70.171 port 38456 ssh2 |
2019-10-13 12:17:38 |
| 222.186.175.220 | attackspam | Oct 13 06:31:09 legacy sshd[6574]: Failed password for root from 222.186.175.220 port 64270 ssh2 Oct 13 06:31:12 legacy sshd[6574]: Failed password for root from 222.186.175.220 port 64270 ssh2 Oct 13 06:31:17 legacy sshd[6574]: Failed password for root from 222.186.175.220 port 64270 ssh2 Oct 13 06:31:22 legacy sshd[6574]: Failed password for root from 222.186.175.220 port 64270 ssh2 ... |
2019-10-13 12:32:07 |
| 81.22.45.51 | attackspam | 10/12/2019-23:58:09.228581 81.22.45.51 Protocol: 6 ET DROP Dshield Block Listed Source group 1 |
2019-10-13 12:03:28 |
| 62.234.131.141 | attackspam | Oct 13 05:52:02 DAAP sshd[14763]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.131.141 user=root Oct 13 05:52:04 DAAP sshd[14763]: Failed password for root from 62.234.131.141 port 57130 ssh2 Oct 13 05:57:18 DAAP sshd[14796]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.131.141 user=root Oct 13 05:57:20 DAAP sshd[14796]: Failed password for root from 62.234.131.141 port 39066 ssh2 ... |
2019-10-13 12:31:33 |
| 80.211.169.105 | attackspambots | Oct 13 00:14:27 plusreed sshd[26934]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.169.105 user=root Oct 13 00:14:28 plusreed sshd[26934]: Failed password for root from 80.211.169.105 port 50220 ssh2 ... |
2019-10-13 12:26:13 |