城市(city): unknown
省份(region): unknown
国家(country): South Africa
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 105.255.250.68
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51790
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;105.255.250.68. IN A
;; AUTHORITY SECTION:
. 145 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022010901 1800 900 604800 86400
;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 12:11:23 CST 2022
;; MSG SIZE rcvd: 107
Host 68.250.255.105.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 68.250.255.105.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 103.240.237.182 | attackbotsspam | Lines containing failures of 103.240.237.182 (max 1000) Oct 2 22:23:54 server sshd[5607]: Connection from 103.240.237.182 port 13041 on 62.116.165.82 port 22 Oct 2 22:23:54 server sshd[5607]: Did not receive identification string from 103.240.237.182 port 13041 Oct 2 22:23:57 server sshd[5611]: Connection from 103.240.237.182 port 10054 on 62.116.165.82 port 22 Oct 2 22:23:58 server sshd[5611]: Address 103.240.237.182 maps to dhcp.tripleplay.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Oct 2 22:23:58 server sshd[5611]: Invalid user admin1 from 103.240.237.182 port 10054 Oct 2 22:23:58 server sshd[5611]: Connection closed by 103.240.237.182 port 10054 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=103.240.237.182 |
2020-10-03 12:02:00 |
| 104.131.110.155 | attackspambots | Oct 3 06:39:36 doubuntu sshd[12773]: Did not receive identification string from 104.131.110.155 port 45172 ... |
2020-10-03 06:58:24 |
| 179.197.71.132 | attack | 1601671289 - 10/02/2020 22:41:29 Host: 179.197.71.132/179.197.71.132 Port: 445 TCP Blocked |
2020-10-03 07:02:00 |
| 190.36.156.72 | attackbots | Unauthorised access (Oct 2) SRC=190.36.156.72 LEN=52 TTL=116 ID=7606 DF TCP DPT=445 WINDOW=8192 SYN |
2020-10-03 07:10:56 |
| 122.51.252.45 | attack | SSH Invalid Login |
2020-10-03 07:21:41 |
| 1.255.48.197 | attack | (From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call. $24.99/mo Flat Fee Credit Card Processing (Unlimited) 1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware? New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019. Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees. 2) You're legally able to demand this new option. Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options? We repre |
2020-10-03 06:58:51 |
| 103.246.240.30 | attackspam | Oct 3 05:55:12 h2829583 sshd[8497]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.246.240.30 |
2020-10-03 12:12:14 |
| 185.216.140.43 | attack | firewall-block, port(s): 50026/tcp, 50039/tcp, 50044/tcp, 50069/tcp, 50092/tcp |
2020-10-03 07:13:05 |
| 190.167.244.87 | attack | Lines containing failures of 190.167.244.87 Oct 2 22:27:15 shared04 sshd[2191]: Did not receive identification string from 190.167.244.87 port 3192 Oct 2 22:27:17 shared04 sshd[2195]: Invalid user user1 from 190.167.244.87 port 3994 Oct 2 22:27:17 shared04 sshd[2195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.167.244.87 Oct 2 22:27:19 shared04 sshd[2195]: Failed password for invalid user user1 from 190.167.244.87 port 3994 ssh2 Oct 2 22:27:20 shared04 sshd[2195]: Connection closed by invalid user user1 190.167.244.87 port 3994 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=190.167.244.87 |
2020-10-03 06:59:52 |
| 35.204.93.160 | attack | RU spamvertising/fraud - From: Your Nail Fungus |
2020-10-03 07:08:17 |
| 114.67.254.244 | attackbots | pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.254.244 Failed password for invalid user mani from 114.67.254.244 port 38272 ssh2 pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.254.244 |
2020-10-03 12:09:33 |
| 137.103.161.110 | spambotsattackproxynormal | I seen as a device I don't own on my device |
2020-10-03 12:17:19 |
| 160.124.103.55 | attack | Oct 3 05:28:26 abendstille sshd\[29296\]: Invalid user service from 160.124.103.55 Oct 3 05:28:26 abendstille sshd\[29296\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.124.103.55 Oct 3 05:28:29 abendstille sshd\[29296\]: Failed password for invalid user service from 160.124.103.55 port 36864 ssh2 Oct 3 05:31:38 abendstille sshd\[32475\]: Invalid user josh from 160.124.103.55 Oct 3 05:31:38 abendstille sshd\[32475\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.124.103.55 ... |
2020-10-03 12:03:43 |
| 45.148.121.92 | attackspam | 45.148.121.92 was recorded 5 times by 4 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 5, 11, 60 |
2020-10-03 12:12:41 |
| 51.254.32.102 | attack | Invalid user mqm from 51.254.32.102 port 42710 |
2020-10-03 07:15:03 |