城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.139.52.111
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47169
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;34.139.52.111. IN A
;; AUTHORITY SECTION:
. 537 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022100700 1800 900 604800 86400
;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 07 23:45:50 CST 2022
;; MSG SIZE rcvd: 106
111.52.139.34.in-addr.arpa domain name pointer 111.52.139.34.bc.googleusercontent.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
111.52.139.34.in-addr.arpa name = 111.52.139.34.bc.googleusercontent.com.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 154.16.53.24 | attack | (From eric@talkwithcustomer.com) Hey, You have a website mikulachiropractic.net, 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 |
2019-12-01 23:28:12 |
| 59.126.239.248 | attackspam | Unauthorized connection attempt from IP address 59.126.239.248 on Port 445(SMB) |
2019-12-01 23:57:09 |
| 185.9.147.100 | attack | Automatic report - XMLRPC Attack |
2019-12-02 00:05:25 |
| 129.213.122.26 | attackspam | Dec 1 16:50:29 legacy sshd[586]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26 Dec 1 16:50:30 legacy sshd[586]: Failed password for invalid user sanne from 129.213.122.26 port 44030 ssh2 Dec 1 16:53:43 legacy sshd[807]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26 ... |
2019-12-02 00:02:43 |
| 176.15.25.52 | attackspambots | Unauthorized connection attempt from IP address 176.15.25.52 on Port 445(SMB) |
2019-12-01 23:49:08 |
| 103.27.9.135 | attackbotsspam | Unauthorized connection attempt from IP address 103.27.9.135 on Port 445(SMB) |
2019-12-01 23:21:07 |
| 200.202.246.178 | attackbots | Unauthorized connection attempt from IP address 200.202.246.178 on Port 445(SMB) |
2019-12-01 23:22:20 |
| 129.213.203.213 | attackbotsspam | 2019-12-01T14:55:38.421863shield sshd\[4883\]: Invalid user steven from 129.213.203.213 port 44422 2019-12-01T14:55:38.426081shield sshd\[4883\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.203.213 2019-12-01T14:55:40.023174shield sshd\[4883\]: Failed password for invalid user steven from 129.213.203.213 port 44422 ssh2 2019-12-01T14:56:32.018889shield sshd\[5003\]: Invalid user kernel from 129.213.203.213 port 42998 2019-12-01T14:56:32.022998shield sshd\[5003\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.203.213 |
2019-12-01 23:59:29 |
| 218.92.0.133 | attackbotsspam | 2019-12-01T15:20:40.549518hub.schaetter.us sshd\[18986\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.133 user=root 2019-12-01T15:20:42.678573hub.schaetter.us sshd\[18986\]: Failed password for root from 218.92.0.133 port 28074 ssh2 2019-12-01T15:20:46.439538hub.schaetter.us sshd\[18986\]: Failed password for root from 218.92.0.133 port 28074 ssh2 2019-12-01T15:20:49.747993hub.schaetter.us sshd\[18986\]: Failed password for root from 218.92.0.133 port 28074 ssh2 2019-12-01T15:20:53.827606hub.schaetter.us sshd\[18986\]: Failed password for root from 218.92.0.133 port 28074 ssh2 ... |
2019-12-01 23:21:57 |
| 41.38.166.172 | attackspambots | SSH invalid-user multiple login try |
2019-12-01 23:26:03 |
| 222.186.180.223 | attack | Dec 1 16:44:26 srv206 sshd[7101]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223 user=root Dec 1 16:44:28 srv206 sshd[7101]: Failed password for root from 222.186.180.223 port 13476 ssh2 ... |
2019-12-01 23:50:12 |
| 190.206.99.225 | attack | Unauthorized connection attempt from IP address 190.206.99.225 on Port 445(SMB) |
2019-12-01 23:35:49 |
| 117.68.195.118 | attackspambots | MAIL: User Login Brute Force Attempt |
2019-12-01 23:41:20 |
| 185.153.197.161 | attack | Port 33896 |
2019-12-02 00:06:16 |
| 128.199.142.138 | attack | Dec 1 16:16:53 [host] sshd[27013]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.142.138 user=root Dec 1 16:16:54 [host] sshd[27013]: Failed password for root from 128.199.142.138 port 46196 ssh2 Dec 1 16:20:24 [host] sshd[27061]: Invalid user nasagov from 128.199.142.138 |
2019-12-01 23:31:39 |